On 2/8/06, Bob Harner <[EMAIL PROTECTED]> wrote: > It is understandably difficult to redesign what is a core part of > Lenya and simultaneously redefine some of the terms being used. Maybe > we need to discuss those things separately, but that would be hard > also. > > Do you all at least share the following goals? > 1. Find a way to treat both the Lenya-managed xml text and binary > files in a (mostly) unified way, so that: > a. both can have historical versions (revisions) > b. both can have a workflow > c. both can have language versions (translations) > d. relationships can be maintained between them (parent/child, > embedding, linking) > e. both can be directly referenced from the navigation menus Yes. We are debating whether to call this class "Resource" or "ContentItem", but I think we all agree with these specifications of functionality.
> 2. Enable/simplify having one web page composed of multiple > separately-managed content. Lenya does that well already: <map:aggregate>. "Modules" will extend the flexibility. > 3. Enable/simplify having multiple web pages for one unit of content > (e.g. an article with 5 pages but managed by Lenya as a single unit) This should not be difficult. Either: - Each section is a separate Document. That is the easiest method with Lenya 1.2. - A Module takes a "Section" parameter to return only a portion of a Document. Some tag needs to be specified as the division point between Sections. > 4. Enable the (optional) use of multiple navigation trees (site trees). I think Indexes should be built into the core as part of the migration to using JCR. I hope it can be done by adding the RelationsTable, the normal "live" hierarchical Index, the SitetreeGenerator, and changing a few Document functions to use the new technology. Support for automatically adding additional Indexes can be added later. The whole functionality could be pushed to the next release if it proves more difficult. > 5. Avoid making such radical changes to the code that a 1.4 release is > overly delayed. Agreed. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
