Acme-CPANModules-PERLANCAR-PluginSystem
view release on metacpan or search on metacpan
{
"abstract" : "List of my modules/frameworks which use a particular plugin system style",
"author" : [
"perlancar <perlancar@cpan.org>"
],
"dynamic_config" : 0,
"generated_by" : "Dist::Zilla version 6.030, CPAN::Meta::Converter version 2.150010",
"license" : [
"perl_5"
],
"meta-spec" : {
"url" : "http://search.cpan.org/perldoc?CPAN::Meta::Spec",
---
abstract: 'List of my modules/frameworks which use a particular plugin system style'
author:
- 'perlancar <perlancar@cpan.org>'
build_requires:
File::Spec: '0'
IO::Handle: '0'
IPC::Open3: '0'
Test::More: '0'
configure_requires:
ExtUtils::MakeMaker: '0'
dynamic_config: 0
Makefile.PL view on Meta::CPAN
# This file was automatically generated by Dist::Zilla::Plugin::MakeMaker v6.030.
use strict;
use warnings;
use ExtUtils::MakeMaker;
my %WriteMakefileArgs = (
"ABSTRACT" => "List of my modules/frameworks which use a particular plugin system style",
"AUTHOR" => "perlancar <perlancar\@cpan.org>",
"CONFIGURE_REQUIRES" => {
"ExtUtils::MakeMaker" => 0
},
"DISTNAME" => "Acme-CPANModules-PERLANCAR-PluginSystem",
"LICENSE" => "perl",
"NAME" => "Acme::CPANModules::PERLANCAR::PluginSystem",
"PREREQ_PM" => {
"strict" => 0
},
NAME
Acme::CPANModules::PERLANCAR::PluginSystem - List of my
modules/frameworks which use a particular plugin system style
VERSION
This document describes version 0.002 of
Acme::CPANModules::PERLANCAR::PluginSystem (from Perl distribution
Acme-CPANModules-PERLANCAR-PluginSystem), released on 2023-07-23.
DESCRIPTION
This is a personal list of my modules/frameworks which use a particular
plugin system style which I will someday extract into its own framework
(Plugin::System). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of
this particular plugin style:
* a plugin can be installed more than once and parameterized (like in
Dist::Zilla or Pod::Weaver) [flexibility];
* execution order of plugins is by priority, then by its order of
activation;
* support for skipping (aborting) an event [flexibility];
ACME::CPANMODULES ENTRIES
Plugin::System
The current name of what the plugin system will be refactored into.
ScriptX
Author: PERLANCAR <https://metacpan.org/author/PERLANCAR>
Started in late 2019, this is the first framework where the I
thought out the rough feature set that I want. ScriptX was written
to eventually replace Perinci::CmdLine: I want a framework that can
be used to write web scripts/form handlers as well as CLI scripts,
with more flexibility in composing behavior/functionality (i.e.
plugin-based). But turns out I haven't had enough time to hack on
it, and making CLI scripts are 99% of what I use Perl for; thus
Perinci::CmdLine lives on for now (with plugins since 1.900).
Perinci::CmdLine::Lite
Author: PERLANCAR <https://metacpan.org/author/PERLANCAR>
While waiting for ScriptX to get into a usable form, I implemented a
similar system to my CLI framework, Perinci::CmdLine starting from
1.900 (released in Oct 2020).
Require::HookPlugin
Another project where I implemented the same plugin system to a
require hook framework. Require::HookPlugin (RHP) was started in
July 2023 because I found hook ordering in Require::HookChain (RHC)
to be fragile and error-prone. Plus, I want more customizability and
composability than what RHC provides.
FAQ
What is an Acme::CPANModules::* module?
An Acme::CPANModules::* module, like this module, contains just a list
of module names that share a common characteristics. It is a way to
categorize modules and document CPAN. See Acme::CPANModules for more
details.
lib/Acme/CPANModules/PERLANCAR/PluginSystem.pm view on Meta::CPAN
package Acme::CPANModules::PERLANCAR::PluginSystem;
use strict;
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2023-07-23'; # DATE
our $DIST = 'Acme-CPANModules-PERLANCAR-PluginSystem'; # DIST
our $VERSION = '0.002'; # VERSION
our $LIST = {
summary => 'List of my modules/frameworks which use a particular plugin system style',
description => <<'_',
This is a personal list of my modules/frameworks which use a particular plugin
system style which I will someday extract into its own framework
(<pm:Plugin::System>). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of this
particular plugin style:
* a plugin can be installed more than once and parameterized (like in <pm:Dist::Zilla> or <pm:Pod::Weaver>) [flexibility];
* execution order of plugins is by priority, then by its order of activation;
* a plugin has a default priority value but the value can be overriden by user [flexibility];
* a plugin has a default event in which it participates, but user can overrides this [flexibility];
* support for repeating an event [flexibility];
* support for skipping (aborting) an event [flexibility];
lib/Acme/CPANModules/PERLANCAR/PluginSystem.pm view on Meta::CPAN
The current name of what the plugin system will be refactored into.
_
},
{
module => "ScriptX",
description => <<'_',
Started in late 2019, this is the first framework where the I thought out the
rough feature set that I want. ScriptX was written to eventually replace
<pm:Perinci::CmdLine>: I want a framework that can be used to write web
scripts/form handlers as well as CLI scripts, with more flexibility in composing
behavior/functionality (i.e. plugin-based). But turns out I haven't had enough
time to hack on it, and making CLI scripts are 99% of what I use Perl for; thus
Perinci::CmdLine lives on for now (with plugins since 1.900).
_
},
{
module => "Perinci::CmdLine::Lite",
description => <<'_',
While waiting for <pm:ScriptX> to get into a usable form, I implemented a
similar system to my CLI framework, <pm:Perinci::CmdLine> starting from 1.900
(released in Oct 2020).
_
},
{
module => "Require::HookPlugin",
description => <<'_',
Another project where I implemented the same plugin system to a require hook
framework. Require::HookPlugin (RHP) was started in July 2023 because I found
hook ordering in <pm:Require::HookChain> (RHC) to be fragile and error-prone.
Plus, I want more customizability and composability than what RHC provides.
_
},
],
};
1;
# ABSTRACT: List of my modules/frameworks which use a particular plugin system style
__END__
=pod
=encoding UTF-8
=head1 NAME
Acme::CPANModules::PERLANCAR::PluginSystem - List of my modules/frameworks which use a particular plugin system style
=head1 VERSION
This document describes version 0.002 of Acme::CPANModules::PERLANCAR::PluginSystem (from Perl distribution Acme-CPANModules-PERLANCAR-PluginSystem), released on 2023-07-23.
=head1 DESCRIPTION
This is a personal list of my modules/frameworks which use a particular plugin
system style which I will someday extract into its own framework
(L<Plugin::System>). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of this
particular plugin style:
=over
=item * a plugin can be installed more than once and parameterized (like in L<Dist::Zilla> or L<Pod::Weaver>) [flexibility];
=item * execution order of plugins is by priority, then by its order of activation;
lib/Acme/CPANModules/PERLANCAR/PluginSystem.pm view on Meta::CPAN
=item L<Plugin::System>
The current name of what the plugin system will be refactored into.
=item L<ScriptX>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
Started in late 2019, this is the first framework where the I thought out the
rough feature set that I want. ScriptX was written to eventually replace
L<Perinci::CmdLine>: I want a framework that can be used to write web
scripts/form handlers as well as CLI scripts, with more flexibility in composing
behavior/functionality (i.e. plugin-based). But turns out I haven't had enough
time to hack on it, and making CLI scripts are 99% of what I use Perl for; thus
Perinci::CmdLine lives on for now (with plugins since 1.900).
=item L<Perinci::CmdLine::Lite>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
While waiting for L<ScriptX> to get into a usable form, I implemented a
similar system to my CLI framework, L<Perinci::CmdLine> starting from 1.900
(released in Oct 2020).
=item L<Require::HookPlugin>
Another project where I implemented the same plugin system to a require hook
framework. Require::HookPlugin (RHP) was started in July 2023 because I found
hook ordering in L<Require::HookChain> (RHC) to be fragile and error-prone.
Plus, I want more customizability and composability than what RHC provides.
=back
=head1 FAQ
=head2 What is an Acme::CPANModules::* module?
( run in 2.904 seconds using v1.01-cache-2.11-cpan-e1769b4cff6 )