hi everyone!
currently, our modules are organized in
modules-core (elementary functionality, must not depend on other modules
outside this tree),
modules (standard functionality, getting quite crowded),
modules-optional (currently unused), and
modules-legacy (modules that don't do stuff as it should be done in 2.0).
i'd like to suggest splitting the existing "modules" directory into
modules-editors (all editors and editor helper modules),
modules-resourcetypes (all resource type modules), and
modules (the rest),
to make it a little easier for new users looking for examples to learn from.
iiuc this can be done simply by adding the appropriate module paths to
build.properties and then bumping its version number to force users to
upgrade their local.build.properties, correct? if it's more intrusive
than that, it's probably not worth it...
wdyt?
as to modules-optional, i'd say let's either use it (for what?) or lose it.
what does "task" in modules-legacy do, and is anyone using it? it's
quite a bunch of code.
iiuc it has been superseded by the usecase framework, and no code in 2.0
is relying on it anymore. any reason to keep it around?
regards,
jörn
--
Jörn Nettingsmeier
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
