Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
On Tue, Feb 17, 2009 at 8:28 PM, Lyle webmas...@cosmicperl.com wrote: Considering that almost everything is already on CPAN, then most plugins are likely to be wrappers, adding extra benefits like lazy loading and framework specific functions. It would be wrong to try and recreate things that are already tried and tested on CPAN. No one is arguing for rewriting things that are on CPAN. Plugins that initially just add lazy loading, will likely grow to take advantage of of other modules and create more framework specific features. The only thing I'm against is a wholesale duplication of huge parts of CPAN's namespace as 10-line modules under CGI::Application::Plugin. If you have unique integration and added value in a plugin, it makes perfect sense. - Perrin # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
On Wed, Feb 18, 2009 at 3:16 AM, Octavian Rasnita orasn...@gmail.com wrote: Using (or creating plugins) for Catalyst is discouraged, because there are better methods for doing the same thing. It was encouraged before it was discouraged. There were dozens of wrapper plugins on CPAN the last time I looked. This isn't really the place for a discussion of Catalyst's model concept. - Perrin # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
From: Perrin Harkins phark...@gmail.com On Tue, Feb 17, 2009 at 12:39 PM, Lyle webmas...@cosmicperl.com wrote: Very easy lazy loaded emailing based on Email::Stuff (with it's new Pure Perl dependency options). I know you mean well with this, but trivial wrappers around other modules described as plugins is the kind of thing that made me stop taking Catalyst seriously. I mean, you could do this sort of plugin for basically everything on CPAN (and Catalyst did). Using (or creating plugins) for Catalyst is discouraged, because there are better methods for doing the same thing. If you were to extract the lazy-loading code into a sort of generic plugin module that can wrap anything and then give Email::Stuff as a SYNOPSIS example, that would be more interesting. - Perrin If the external module can be wrapped as a model, there are Catalyst::Model::Adapter, Catalyst::Model::Factory and Catalyst::Model::Factory::PerRequest generic modules that can make the external module be a model. For example, the email-sending module Mail::Builder::Simple can be used in Catalyst as a model with the help of the generic module Catalyst::Model::Factory, and for beeing even more simple to use it, I've created the helper module Catalyst::Helper::Model::Email that creates that model, but Mail::Builder::Simple is very easy to configure, so that helper doesn't do very many things. Octavian # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
[cgiapp] [Announce] CGI::Application::Plugin::Email
Hi All, Very easy lazy loaded emailing based on Email::Stuff (with it's new Pure Perl dependency options). Lyle # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
nice stuff. will try it later. On Tue, Feb 17, 2009 at 3:39 PM, Lyle webmas...@cosmicperl.com wrote: Hi All, Very easy lazy loaded emailing based on Email::Stuff (with it's new Pure Perl dependency options). Lyle # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## #### # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
On Tue, Feb 17, 2009 at 12:39 PM, Lyle webmas...@cosmicperl.com wrote: Very easy lazy loaded emailing based on Email::Stuff (with it's new Pure Perl dependency options). I know you mean well with this, but trivial wrappers around other modules described as plugins is the kind of thing that made me stop taking Catalyst seriously. I mean, you could do this sort of plugin for basically everything on CPAN (and Catalyst did). If you were to extract the lazy-loading code into a sort of generic plugin module that can wrap anything and then give Email::Stuff as a SYNOPSIS example, that would be more interesting. - Perrin # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
Re: [cgiapp] [Announce] CGI::Application::Plugin::Email
Perrin Harkins wrote: On Tue, Feb 17, 2009 at 12:39 PM, Lyle webmas...@cosmicperl.com wrote: Very easy lazy loaded emailing based on Email::Stuff (with it's new Pure Perl dependency options). I know you mean well with this, but trivial wrappers around other modules described as plugins is the kind of thing that made me stop taking Catalyst seriously. I mean, you could do this sort of plugin for basically everything on CPAN (and Catalyst did). Considering that almost everything is already on CPAN, then most plugins are likely to be wrappers, adding extra benefits like lazy loading and framework specific functions. It would be wrong to try and recreate things that are already tried and tested on CPAN. Plugins that initially just add lazy loading, will likely grow to take advantage of of other modules and create more framework specific features. For example C::A::P::I18N is a lot more than a wrapper around Locale::Maketext::Simple, and another plugin I haven't released yet for Date and Time methods has already had extra C::A functions added. If you were to extract the lazy-loading code into a sort of generic plugin module that can wrap anything and then give Email::Stuff as a SYNOPSIS example, that would be more interesting. I've been thinking this method would work for a lot of modules, although for some it's a bit more tricky (look at C::A::P::YAML). Lyle # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp## #### ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ####
