I still cannot decide where sources and configuration for an
application should be placed, so I ask the community for help again.
Description:
============
It is already decided, by an earlier vote, in which directory
structure certain 'non-core' code must reside. Taking the 'media'
project as example that would be org.mmbase.applications.media.
But well, now I still don't know what to do.
The media project's code now can be found in 'speeltuin', which is
obviously not a so very swell place.
I have two proposals:
1 . A new CVS module 'applications' in which for every application a
directory can be created. Like 'media', and e.g. media builders
can then be found in
'applications/media(|/src)/org/mmbase/applications/media/builders'.
The advantage of this is that applications are garantueed to be
relative to each other defined by the 'applications' module, and
dependencies and general functionality can be defined.
The disadvantage is that such an application does not seem to be
optimally stand-alone. Perhaps though alias modules can be created
if necessary which check out only the relevant part.
2. A new CVS module for every application. For the media-project that
would e.g. be 'media'. This will perhaps avoid unnecessarily deep
directory trees. For dependencies to work, it should perhaps be
make configurable or prescribed, where other code is relative to
this directory.
I myself like (1) slightly better. But well, go ahead, please:
[ ] I prefer one CVS module 'applications' with a sub-directory for
every (non-core) project
[ ] I prefer a seperate CVS module for every (non-core) project
[ ] I have a better idea, namely: ..............................
START OF CALL: 2003-04-02
END OF CALL: 2003-04-05
If this is settled, the 'media' project can be moved from speeltuin,
and I think also the things currently in 'src/org/mmbase/applications'
can be moved to (applications/) dove, editwizard, xmlimporter.
Michiel
--
mihxil' Michiel Meeuwissen
Mediapark C101 Hilversum
+31 (0)35 6772979
[]()
