[Padre-dev] [Padre-commit] rev 786 - in trunk/lib/Padre/Plugin: . Development

[Steffen Mueller]

Hi Jerome,

Jerome Quelin wrote:
> we can see more and more padre plugins on cpan, but couldn't they have
> their development in padre svn and be released with padre distribution?
> 
> i can see some advantages:
> - some enhancement requests for padre are better tackled with plugins.
>   therefore, having the plugins within padre svn allows for better
>   interaction with trac

Yes, that makes sense. There are a couple of plugins in the Padre svn 
repository (albeit not in the Padre trunk).

It's simply that not everybody who might want to write and publish a 
plugin necessarily has (nor wants) commit access to the repository.


> - people wanting to try padre want to have all the plugins goodness, and
>   it's easier for them to install a single module rather than padre plus
>   a bunch of other modules.

Installing Padre with a bunch of default plugins is still possible by 
publishing a Task::Padre or Plugin::Padre. There is one thing that 
bothers me: You can't simply make Padre depend on the plugins as those 
depend on Padre...

While I'm at it, to all the plugin authors who use Module::Build:

Padre contains a class "Padre::PluginBuilder" which is a Module::Build 
subclass that adds two targets:

./Build plugin (creates Foo.par if the plugin name is "Foo")
./Build installplugin (creates and installs the .par into the user 
.padre directory)

You can use it in place of Module::Build and add a configure_requires 
dependency on Padre. For an example, see Padre::Plugin::PAR 0.04 (almost 
on CPAN) or in the Padre SVN repository.

Cheers,
Steffen