On 8/9/06, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote:
Andreas Hartmann wrote:
> Hi Lenya devs,
> documents are now stored in the following structure:
> content/<area>/<uuid>/<language>
> <language>.meta
> Example:
> content/authoring/550e8400-e29b-11d4-a716-446655440000/de
> de.meta
> en
> en.meta
> I chose this structure because it is reduced to the essential
> information and IMO it is quite straightforward - all translations
> of a document and their meta data share a directory.
>
> Do you agree to this, or would you prefer a different structure?
looks neat.
side question: is the area concept now fixed "forever", or will it be
possible to re-discuss it after 1.4 is out without affecting too much of
your current storage layer work? i still have the gut feeling that we
should get rid of the areas altogether.
Joern,
I believe you will be very happy with Lenya 1.3. 1.3 removes Areas;
it uses that portion of the URL for the module. 1.3 adds Revisions,
which make publishing and rollback incredibly easy. 1.3's content
structure is based on UNIDs (or UUIDs), and uses Structures to
maintain hierarchies. Today, you can see how content works with File
and Link resources. Editing XML resources will be added soon; the
code is half written, but I was unable to work on it for the last two
weeks. I am uncertain there will be an upgrade path from 1.4 to 1.3;
content should be easy, but Modules have very different internals.
Hopefully we can merge 1.4's ability to have Module-specific Java
class files if that feature proves useful.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
