Baltasar Cevc wrote:


A. Pagaltzis wrote: > * Baltasar Cevc <[EMAIL PROTECTED]> [2005-03-10 13:25]: >> use Modularizer; > Well, I can't think of anything really helpful right now, but I > have to register that that name is pretty horrible. It should > definitely be in Module:: and mention Plugin somehow. Maybe > something like Module::Plugin::Framework (or ::PluginFramework), > though I don't know about that.

Thanks for your informations.

I agree on the first point ;-)

However, Module:: does not seem like a matching "category" to me.
Apart from some modules that could live anywhere else, too,
Module:: contains modules related to packaging, locating and
extending perl modules.
The approach of the code I wrote is to split up an application
into modules or plugins or whatever one may call it.
Framework sounds good and matches what the code does, I would say.

Greetings from the finally sunny city of Regensburg, Germany

Baltasar

App::Pluggable? Or, reconsidering your words ("Module::Pluggable concentrates on bringing some modules together, whereas my module is written from the point of view of somebody splitting an application into modules"), perhaps App::Modular.


Lastly, since it looks like your functionality automatically loads modules on deman, perhaps App::AutoLoading.

Wow. I've always been OCD about properly naming variables/functions/modules/tables/columns/etc. I can see this group becoming addicting.

-ofer

Reply via email to