> 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 :)
You're right. It would be like trying to combine two different ways to do the same thing : Cocoon and Laszlo are both for the presentation layer, but Cocoon is MVC whereas Laszlo is not, so piping Cocoon M and C into a Laszlo V would require Laszlo to be MVC itself, which it's not and it's normal as it' doesn't need to be : MVC fits for the classical Web, not for that new kind of RIA's. I guess the best thing is to make a choice. It's already amazing what you can do with this incredible framework. For example, I haven't tried it yet, but it seems that you can connect a Laszlo presentation layer with a Spring business layer through JavaRPC. In fact it depends on what your priority is. If you want accessibility and multichanneling first, Cocoon is the best choice. If user experience is your main concern, Laszlo is excellent. And this user-experience concern is becoming very present : think of XUL or XAML, they do exactly the same as Laszlo, except that those two are not portable between browsers... -- Sébastien Arbogast Blog : http://www.sebastien-arbogast.com The Epseelon Project : http://www.epseelon.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
