On Fri, Feb 11, 2011 at 3:47 PM, Sebastian Willing <sebastian.will...@web.de> wrote:
> > I don't see people installing Plugins. Things like "svn" and "tidy" and > other mandatory issues are installed, but many others are very unknown > to Padre users. That needs to be solved in other ways, not by pulling them into trunk. Are they stable? If so someone could create and "educational kit" for them. E.g. a screencast? > Option #2 sounds best to me. The Padre::Plugin::Experimental(Features) > should be a core plugin. It could be enabled by default when running > trunk and disabled by default when running a released version. Making it into core will easily drag more dependencies into core which we want to avoid. I think people who care will invest the energy to install a plugin but we should make it much easier. e.g. the plugin manager could show a list of available plugins that could be installed from CPAN and it could have an option to "install plugin". We "just" need to fix the CPAN integration of Padre. Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
