Event:...rontend(3pm)

πŸ’– Event::ExecFlow::Frontend πŸ’–

okay so bestie, welcome to the Event::ExecFlow::Frontend page πŸ’… β€” it's from the User Contributed Perl Documentation, section 3pm, which is basically the group chat where Perl people drop their own docs. and this one? this one is an abstract base class, which is fancy-speak for "you don't use me directly, you build on me." main character energy only ✨


🌸 NAME 🌸

Event::ExecFlow::Frontend β€” Abstract base class for custom frontends πŸŽ€


✨ SYNOPSIS ✨

#-- Derived from Event::ExecFlow::Frontend
my $frontend = MyApp::GUI::Frontent->new();
my $job      = Event::ExecFlow::Job::Command->new ( ... );
$frontend->start_job($job);

#-- Later the following methods are called and need to
#-- by implemented by you
$frontend->report_job_start($job);
$frontend->report_job_progress($job);
$frontend->report_job_error($job);
$frontend->report_job_warning($job);
$frontend->report_job_finished($job);
$frontend->log($message);

like, you make your own subclass, you hand it a job, and then it's your turn to fill in all those report_* and log methods. no skipping bestie, the framework is literally going to call them and if they're not there it's giving πŸ’€


πŸ¦‹ DESCRIPTION πŸ¦‹

so this is an abstract base class and honestly you're usually not calling it straight from your app. it's the chill background vibe.

but for your day-to-day programming, the attributes defined in this class are the ones that matter most, because they're common to all Jobs of the Event::ExecFlow framework β€” every single job shares them, no cap πŸ’–


πŸ‘‘ OBJECT HIERARCHY πŸ‘‘

Event::ExecFlow

Event::ExecFlow::Job
+--- Event::ExecFlow::Job::Group
+--- Event::ExecFlow::Job::Command
+--- Event::ExecFlow::Job::Code

Event::ExecFlow::Frontend
Event::ExecFlow::Callbacks
Event::ExecFlow::Scheduler
+--- Event::ExecFlow::Scheduler::SimpleMax

look at that little family tree 😭 Event::ExecFlow::Job has three babies, and Event::ExecFlow::Scheduler has one. Frontend, Callbacks and Scheduler just be hanging out at the top level. iconic honestly.


πŸ’… METHODS πŸ’…

[ FIXME: describe all methods in detail ]

yep. that's the whole section. the author said "coming soon" and never came back πŸ™ˆ we still love them tho 🫢


🫢 AUTHORS 🫢

Jârn Reder <joern at zyn dot de> ⭐


Copyright 2005-2006 by JΓΆrn Reder.

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details.

You should have received a copy of the GNU Library General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307 USA.

no warranty bestie, fr fr β€” read the license, it's literally right there πŸ’–

πŸ’€ POD ERRORS πŸ’€

Hey! The above document had some coding errors, which are explained below:

Around line 123:

  • Non-ASCII character seen before =encoding in 'JΓΆrn'. Assuming CP1252

not the umlaut causing drama in the POD parser 😭 the â said "I'm built different" and Perl was like "sure, CP1252 it is." periodt.


and that's the whole page babes 🌈 written by JΓΆrn Reder, living in the User Contributed Perl Documentation, rendered by perl v5.38.2 on 2024-02-17, filed under Event::ExecFlow::Frontend(3pm). go build a frontend, you got this πŸ’œβœ¨

πŸ“¦ where this page comes from