Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by AndreasHartmann: http://wiki.apache.org/lenya/ProposalLenya2%2e0 ------------------------------------------------------------------------------ == Andreas Hartmann's Wishlist == - === Developer-centric wishlist items === + === Complaints === - * drop the concept of separated scheduler servlet (DONE) - * introduce clean and stable CMS function concept (DONE) + * 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. + + === Suggestions === + + ==== 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 == Torsten Schlabach's Wishlist == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
