That is very useful. Sadly my task at hand needs some server push data. What you suggested is like a lazy init. So after the page loaded go and get some content. (If I understood you correctly)
I am comming form the GWT world and there is a need to drop GWT for this project. So I need to learn it the JS + Tapestry way. Passing Link information is quite an interesting idea. One could also use something like comments. Back in the old days (08) we stored information in comment blocks and used GWT/JS to read those configurations. The configurations where actually components using there own markup writer instead of templates. Works wonders but might be a bit odd. So currently i would like to have some sort of server push. How is the tapestry way of doing server push functionality? On autocomplete you just issue http requests right? Maybe I should study the Tapestry documentation on this one... . 2013/8/16 Lance Java <lance.j...@googlemail.com> > I agree it's not easy, but just wanted to put it up for discussion. > > I think that having a clientside function could simplify many components. > Generating a serverside link then passing it through as javascript > initializer on the client adds extra code each time. I've done this many > times in many components. I've often thought it would be nice to generate > the link clientside instead. > On 16 Aug 2013 14:14, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> > wrote: > > > On Fri, 16 Aug 2013 09:01:37 -0300, Lance Java < > lance.j...@googlemail.com> > > wrote: > > > > It would be nice to have a javascript function to generate event URL's. > >>>> > >>> > >> That would need a JavaScript implementation of UrlEncoder, which is an > >>> > >> overridable service. > >> > >> Validators have both a clientside and a serverside implementation. > Perhaps > >> UrlEncoders could do the same? > >> > > > > I guess so. Since @RequestParameter, I'm not sure if it's worth to be > > implemented, as even after that we'd still need to take care on how to > add > > the event activation context without messing up with other stuff, > specially > > the t:ac query parameter which contains the page activation context. > > > > -- > > Thiago H. de Paula Figueiredo > > > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org< > users-unsubscr...@tapestry.apache.org> > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
