Main difference as I see it. Plugins can't use the configuration subsystem, core features can.
That includes the ability to define project-specific configuration. We already cheat quite badly and have a core setting for the perltidy file location. Personally, in this case, I think if we are going to ship it in the core distribution then PerlTidy doesn't add enough functionality to reallly justify being a plugin and there's quite a lot of benefits to having it in the core. Adam K On 15 February 2011 08:51, Claudio Ramirez <padre.clau...@apt-get.be> wrote: > Hi, > > There are some people (ok: me :) ) that would love to see the > Perl::Tidy plugin move into core. The dependencies look ok (thx, Alias!). > > I have a few questions: > > - Are there any features that need to be implemented or bugs fixed > before we integrate it into core? > > - Furthermore, with the development process discussion in mind, would > this be a good candidate to help us document a "plugin to core > migration" as a reference for other plugins? > > - If the owners of the Padre plugin are reading this, what do you think > about this request? > > Claudio > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
