Jörn Nettingsmeier wrote:
don't get me wrong, i don't want to be disrespectful,
don't worry
but the fact is that despite its considerable age 1.4 is still a pile
of patchwork with many open issues, and at least to me it is not clear
where the journey is heading...
to me it's very clear:
- generic request2process mapping API (whereas Cocoon could be an
implementation)
- navigation framework
- resource type framework
there is still no release date, and core parts are constantly being
gutted and re-written (which is not bad at all, just irritating when
you've been told a year ago that it would be perfectly sane to base a
project on lenya 1.4 :-D)
agreed. Well, I am using it in production, but I think the current
changes are
really done very in a very bad way (even if they might be meant as a
good thing or maybe turn out to be good), but no real discussion has
been held and they break a lot of stuff although I don't see any reason
why this is actually necessary, because it could have done way different
hacking something into the core because you need it (and you happen to
be a core developer) might not be the best approach. rather keep the
core clean and use a branch for the particular project that needs i18n
hrefs, at least until there is a global consistent concept of
"i18nized everything" throughout lenya (i.e. for all assets, for urls
and whatnot). at the moment, i still need to patch the core code to
make i18n work in templated publications, and that seems a rather more
pressing issue for me.
I don't fully understand. Can you explain a bit?
Michi
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
