Re: [RT] Modernizing CForms

Daniel Fagerstrom wrote: > Sylvain Wallez skrev: >> A very concrete example: within a Wicket application, we needed to have >> areas of the screen be the result of the transformation of some XML >> document. We ended up doing coding pipelines in plain Java. If Cocoon >> had provided a simple way

Re: [RT] Modernizing CForms

Grzegorz Kossakowski skrev: Sylvain Wallez napisał(a): Grzegorz Kossakowski wrote: The "IE gives me shudders" feeling is partly one of the reasons for Ajax toolkits to exist. This unfortunately doesn't solve everything, but helps a lot! This only partly address my doubts. I really ask about t

Re: [RT] Modernizing CForms

Sylvain Wallez skrev: Daniel Fagerstrom wrote: I don't propose that we should throw out the current Forms framework. What I do propose is that it could be improved so that it would require less work to use and so that it would support AJAX+REST style webapps better. Don't repeat yourself =

Re: [RT] Modernizing CForms

Jorg Heymans napisał(a): > Grzegorz Kossakowski wrote: > >> I recall some discussion about it in the past. Does it mean that even >> we integrate Dojo into cocoon-forms very nicely user will be forced >> to break all the modularity and use the compressor? Am I missing >> something? >> > > Aggregati

Re: [RT] Modernizing CForms

Grzegorz Kossakowski wrote: I recall some discussion about it in the past. Does it mean that even we integrate Dojo into cocoon-forms very nicely user will be forced to break all the modularity and use the compressor? Am I missing something? Aggregating and compressing [1] the required dojo

Re: [RT] Modernizing CForms

Sylvain Wallez napisał(a): Grzegorz Kossakowski wrote: The "IE gives me shudders" feeling is partly one of the reasons for Ajax toolkits to exist. This unfortunately doesn't solve everything, but helps a lot! This only partly address my doubts. I really ask about the prospects for AJAX. If I'

Re: [RT] Modernizing CForms

Grzegorz Kossakowski wrote: > Daniel Fagerstrom napisał(a): > >> I don't propose that we should throw out the current Forms framework. >> What I do propose is that it could be improved so that it would >> require less work to use and so that it would support AJAX+REST style >> webapps better. >>

Re: [RT] Modernizing CForms

Daniel Fagerstrom napisał(a): > > I don't propose that we should throw out the current Forms framework. > What I do propose is that it could be improved so that it would > require less work to use and so that it would support AJAX+REST style > webapps better. > > Don't repeat yourself > ===

Re: [RT] Modernizing CForms

Daniel Fagerstrom wrote: > I don't propose that we should throw out the current Forms framework. > What I do propose is that it could be improved so that it would > require less work to use and so that it would support AJAX+REST style > webapps better. > > Don't repeat yourself > =

[RT] Modernizing CForms

Grzegorz Kossakowski skrev: Daniel Fagerstrom napisał(a): Grzegorz Kossakowski skrev: ... A modern form framework === Being a little bit provocative I'm starting to find CForms rather old fashioned in style. Why so much server side stuff wouldn't it be better with a form