Andreas Hartmann wrote:
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.
oh-oh. you never know what you're up against in the ghastly depths of a
release process (quoting gandalf the white, "RUN, YOU FOOLS!" :-D )
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!
thanks to you for all those awesome hacking fits!
But of course there's much room for improvement:
<snip>
Here are some points from my wishlist:
Move to Java 5
--------------
I'd really like to use generics and all the other nifty stuff.
+1
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.
+2
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.
+4
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 don't have that much of a problem with lenya's speed atm. the greatest
problem is that sitetree gets bog slow when the number of documents
increases. some ajax should fix that. snappier is always cooler, but
power users can use DAV (which we should test more!), and some batch
commit mode would be nice... but for me, making lenya a little more
feature complete and a lot more robust (especially the editors) is far
more important.
but as to cleaning up and simplifying pipelines, +8
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.
i don't think this trade-off exists. editing need not be slow. we need a
good editor abstraction layer, so that we can stop reinventing wheels,
delegate the basic rendering of a to-be-edited page to the publication,
add some editor-specific quirks, and there we go. caching of editor code
should take care of the load times...
Stable, Out-of-the-Box Repository
---------------------------------
<snip, see other thread>
regards,
jörn
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
