[EMAIL PROTECTED] wrote:
On 2/28/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
I think to make things clearer what is really needed by the core
we should split the modules dir into:
modules-core
modules-shared
This should rather be solved by declaring dependencies.
The "core module" can declare other modules it depends on.
These modules may not depend on the core module.
I have not looked at the official implementation, but having all Lenya
Modules in a "modules" directory made my implementation easy. Is
there a reason to separate them?
You suggested a "module.xml" descriptive file to each Module. That
file could contain "type" fields. I recently posted a list of "types"
of Modules: Admin, ResourceTypes, Editors, NavigationElements, Pages,
and Backend. A "type" field could be used by the Publication
ModuleChooser screen.
I agree. If we categorize modules, this should be done using
meta data, not directories.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
