Jeje, thx for the feedback, Ross. salu2
El mié, 19-10-2005 a las 11:09 +0100, Ross Gardler escribió: > Thorsten Scherler wrote: > > El mié, 19-10-2005 a las 09:52 +0100, Ross Gardler escribió: > > > >>Thorsten Scherler wrote: > >> > >>>Hi all, > >>> > >>>lately I worked with AJAX and would like to support v2 with AJAX > >>>out-of-the-box. > >>> > >>>WDYT? > >> > >>What is the use case? > > > > > > ATM no actual use case, but we can use it in e.g. the search contract > > and enable the google suggestions > > http://www.google.com/webhp?complete=1&hl=en. AJAX in general is really > > useful and I have tons of ideas around it. ;-) > > I see it is exciting - but I'd rather finish what we started first (I > just mean I don't have the time for that, but if you do, OK). > > >>It seems to me that with this Forrest would be moving a long way from a > >>publishing framework and becoming more like Cocoon itself, an > >>application framework. But maybe I'm just bind to the use case. > > > > > > Hmm, IMO no. contracts are extra-content and/or extra-functionality. > > AJAX is just a way to update parts of the site on user interaction > > without having to reload the whole site. > > OK, got that - good idea. > > >>>There is a ajax-block in cocoon, which is the best way to incorporate > >>>this in existing structurer? > >> > >>We need Forms to be working first. > > > > > > Why do you think so? > > > > Forms depend on AJAX (not the other way around, have a look at > > blocks.properties). > > Really! My mistake then. > > >>>Or is it better to create a new plugin? > >> > >>If we make Forrest a Cocoon block then we get to use the Ajax block > >>however we want. > >> > > > > > > Actually AJAX support is just linking a couple of jscripts by default in > > the view. Thinking about it the easiest way is to write a contract for > > that. > > Off you go then, I expect to see a cool demo tomorrow morning ;-) > > Ross > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
