Hi Lenya devs, there are still some months left until the developers meeting in Zurich, but as we all know time tends to go by faster than one thinks. Maybe it's worth collecting some ideas until we meet, so that we have something to start with when discussing the roadmap.
IMO 1.4 is quite settled now, apart from the obvious bugs. I have to admit that I'm quite pleased with the latest developments. The implementation of modules doesn't require to touch the core anymore (except from bugfixes). The code base is much cleaner than it used to be. Thanks to all of you who were involved! But of course there's much room for improvement: - It's still to complex to write usecases (too much configuration). - It's terribly hard to access document properties or meta data, not to mention queries, dynamic aggregation etc. - The authoring environment is much too slow. - ... I'd like to get a feeling in which direction the Lenya project is likely to move. So I'm raising these issues now to see if you have similar thoughts or completely different ideas. Here are some points from my wishlist: Move to Java 5 -------------- I'd really like to use generics and all the other nifty stuff. Convention over Configuration ----------------------------- I used to prefer configuration for a long time for reasons of flexibility, but I kind-of changed my mind. We have to make flexibility trade-offs to accelerate development. The past showed that many configuration options are apparently not important enough to be worth providing. Consolidate, Re-Use Concepts ---------------------------- Instead of developing new concepts, we should rather re-use existing ones. A good example was Joern's note to use content items for inbox message storage. An example how not to do it is the rank growth of editor integrations. Clean and Fast Authoring Environment ----------------------------------- Currently, the authoring environment carries out a lot of Cocoon pipeline processing which is necessary to generate the WYSIWYG view, which makes it terribly slow. The same is true for the site environment. I'm convinced that we could implement something faster (and probably easier to maintain) using JSF and AJAX, or by radically simplifying and stripping down our pipeline architecture. I'd be happy to live without true WYSIWYG when I get in-place editing of page titles and meta data (like Flickr and the like) and can navigate end edit faster. Stable, Out-of-the-Box Repository --------------------------------- With our homegrown repository implementation we'll never be able to meet any enterprise requirements. We need true transactions and performant querying. Some options: - JCR - Shared-nothing architecture with JPA / Hibernate - EJB 3.0 These are the most important points that come into my mind. I'm interested in your thoughts. But of course we should focus on getting 1.4 out first, before getting lost in discussions :) -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
