True, i tried a few exemples and the first generation is really slow for
just a hello world :-\
the good this is that the cocoon caching system seems to work fine with
lazlo, so depending on how the pipes are designed and optimized for
caching, this can remain a small problem.
For me, the main difficulty i see is to have underlying "logical"
documents that fit with both lazlo and html view. The problem will
always be to match this or this lazlo feature (like window or layout) in
html+css. Proably a lot of headaches here, but really worth it :)
Marc
Sebastien Arbogast a écrit :
I see it also like that, cocoon is a MVC framework that handles easily
multiples V, why not using lazlo for at least one of the views of the
webapp ?
Exactly ! That could make accessibility go a step further : you make a
RIA V and for those who don't want or don't like Flash, you just make
an AJAX or plain XHTML one, without having to develop all the rest
again. Moreover, I think that OpenLaszlo misses a few features that
Cocoon provides, like i18n for example (their support for resources is
quite... simple), so we could translate lzx files before passing them
to LZX compiler.
The big problem I see with this collaboration is that performance is
already a big issue with Laszlo. So with Cocoon XML transformations
before, it could be awful.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
