I saw it, but unless I use the superloader, it still need to define the
names of the modules I want to use.And, regarding the superloader, I'm lazy
enough to want to use all the packages within a given folder, but not just
every possible module in the world...
Still, a good suggestion.
On Fri,
Porta wrote:
I saw it, but unless I use the superloader, it still need to define the
names of the modules I want to use.And, regarding the superloader, I'm lazy
enough to want to use all the packages within a given folder, but not just
every possible module in the world...
Still, a good
nicemuch closer, indeed.
On Fri, Jun 12, 2009 at 10:09 AM, Michael Peters mpet...@plusthree.comwrote:
Porta wrote:
I saw it, but unless I use the superloader, it still need to define the
names of the modules I want to use.And, regarding the superloader, I'm
lazy
enough to want
Michael Peters wrote:
Porta wrote:
I saw it, but unless I use the superloader, it still need to define the
names of the modules I want to use.And, regarding the superloader, I'm lazy
enough to want to use all the packages within a given folder, but not just
every possible module in the world...
Rhesa Rozendaal wrote:
Heh, I use Module::Pluggable for that in my startup.pl:
use Module::Pluggable require = 1, search_path = [qw(
My
Other::Stuff
)];
__PACKAGE__-plugins;
That would load everything under My::* and Other::Stuff::*.
Can Module::Pluggable be used as an alternative to
On Fri, 12 Jun 2009, Richard Jones wrote:
Can Module::Pluggable be used as an alternative to Module::Find? I load all
my Model::DB classes up front in a BEGIN block in MyApp::Base, like this:
BEGIN {
use Module::Find;
Module::Find::setmoduledirs('path/to/lib');
Module::Find::useall
Hey, folks.
Question:
I was wondering if anyone else (than me) thinks is annoying to declare the
use of all the required models (objects? packages?) you're using in your
CA app?More, when working with CAD, on each controller you need to repeat
use MyApp::Foo; use MyApp::Bar; etc.
Assuming you're
On Thu, Jun 11, 2009 at 11:11 AM, Portajulian.po...@gmail.com wrote:
Hey, folks.
Question:
I was wondering if anyone else (than me) thinks is annoying to declare the
use of all the required models (objects? packages?) you're using in your
CA app?More, when working with CAD, on each controller
P Kishor wrote:
What I do find annoying is the number steps involved in adding a new
run mode, esp. when using CAD.
First, add the new run mode to the dispatch table.
Second, add the run mode to the setup in the module (assuming one is
not using AutoRunmode... some problems have been alluded
Porta wrote:
Hey, folks.
Question:
I was wondering if anyone else (than me) thinks is annoying to declare the
use of all the required models (objects? packages?) you're using in your
CA app?More, when working with CAD, on each controller you need to repeat
use MyApp::Foo; use MyApp::Bar; etc.
Porta wrote:
Hey, folks.
Question:
I was wondering if anyone else (than me) thinks is annoying to declare the
use of all the required models (objects? packages?) you're using in your
CA app?More, when working with CAD, on each controller you need to repeat
use MyApp::Foo; use MyApp::Bar; etc.
On Thu, Jun 11, 2009 at 12:26 PM, Rhesa Rozendaalp...@rhesa.com wrote:
P Kishor wrote:
What I do find annoying is the number steps involved in adding a new
run mode, esp. when using CAD.
First, add the new run mode to the dispatch table.
Second, add the run mode to the setup in the module
P Kishor wrote:
[..]
Hi Rhesa, CAP::RunmodeDeclare looks very interesting. I actually used
CAP::AutoRunmode successfully, but I remember seeing a thread on this
mailing list itself about CAP::AutoRunmode causing problems under
certain circumstances, particularly under mod_perl.
Perhaps you
Are you perhaps looking for Class::Autouse? Not something I would use
myself, but it may help you be more lazy in your programming...
Cheers,
Cees
On Fri, Jun 12, 2009 at 2:11 AM, Porta julian.po...@gmail.com wrote:
Hey, folks.
Question:
I was wondering if anyone else (than me) thinks is
14 matches
Mail list logo
