On Sunday, October 21, 2012, Dragan Sahpaski wrote: > The main javascript API we've been using is Tapestry.Initializer, > which I think should be kept for backwards compatibility. > Probably the best is to deprecate javascript APIs in 5.4 and remove > them in 5.5 as it's the tapestry way of doing with java public APis. I > hope require js will allow us to write more modular javascript but > also it's my opinion that tapestry should use it as much as possible > to introduce a public javascript API that is like a very small utility > library that has good documentation.
Definitely paying attention to documentation now. Many things that used to require generating a unique id and invoking an initializer function are now just a matter of including a specific data- attribute in the element (and possibly including a specific module via JavaScriptSupport.require() ). I'm pretty jazzed about that. > How many users have asked on the > mailing list how to trigger an ajax form submit to do a zone update > etc. > > I think that is very good idea; keep enough around that apps using the initializer function infrastructure can continue to operate. > Thanks, > Dragan Sahpaski > > > On Sun, Oct 21, 2012 at 8:54 PM, Bob Harner > <[email protected]<javascript:;>> > wrote: > > Maybe the Tapestry and T5 namespaces could be replaced with "dummy" > > implementations that provide alerts or JS console error messages that > > contain helpful hints about how to migrate to the new 5.4 code? > > > > I'm very concerned about the migration effort. No matter how wonderful > > 5.4 turns out to be, if upgrading apps isn't easy then we'll lose a > > certain percentage of our users. > > > > On Sun, Oct 21, 2012 at 12:50 PM, Howard Lewis Ship > > <[email protected]<javascript:;>> > wrote: > >> On Sunday, October 21, 2012, Massimo Lusetti wrote: > >> > >>> On Sat, Oct 20, 2012 at 8:02 PM, Kalle Korhonen > >>> <[email protected] <javascript:;> <javascript:;>> wrote: > >>> > >>> > Well, it was undocumented anyway so no reason to go overboard with > >>> > compatibility if it's that big of a problem. Assuming all other > things > >>> > are reasonably well backwards compatible and we have the main > >>> > libraries up-to-date at GA, it'll be just something that we need to > >>> > communicate to the community. > >>> > >>> For what I've seen in the code that seems the actual issue and I agree > >>> with you in the way it should addressed. > >>> I will try to produce an alpha asap to let a broader audience to look > >>> at and then check the feedback. > >> > >> > >> > >> I think it is early for an alpha, as many components are broken > currently > >> as we are mid-transition. > >> > >> I do want to get a preview out soon. > >> > >> > >>> > >>> For what is my own part a small amount of work on the js side of my > >>> apps should let me upgrade to future 5.4 > >>> > >>> Cheers > >>> -- > >>> Massimo > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: > >>> [email protected]<javascript:;><javascript:;> > >>> For additional commands, e-mail: > >>> [email protected]<javascript:;> > <javascript:;> > >>> > >>> > >> > >> -- > >> Howard M. Lewis Ship > >> > >> Creator of Apache Tapestry > >> > >> The source for Tapestry training, mentoring and support. Contact me to > >> learn how I can get you up and productive in Tapestry fast! > >> > >> (971) 678-5210 > >> http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected]<javascript:;> > > For additional commands, e-mail: [email protected]<javascript:;> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected]<javascript:;> > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
