On Dec 19, 2005, at 9:10 PM, Cees Hek wrote:
I think what Mark has in mind is a system where any non-config plugin can depend on a standard place to find configuration info.
I've put my config info in a module and call it in my instance script like so:
use APP::SetUp 1.0; Then I use this info in my app script like so: $output .= $APP::SetUp::page_footer; Is this what you mean by "or just provide it from some global perl configuration variables"? If not, Is there anything wrong with what I'm doing?In any case, I'd really like to see something like "$self->config" with a simple example of a config file. If you mean I can change the above to:
$output .= $self->config('page_footer');
This make perfect sense to me. It "feels" (to me) like this should be
basic piece of any solid framework, and I think it would make it easier
to setup even small apps.
Cheers,
Bill
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.