Hi all, One more reason in favor of supporting jQuery (exclusively or among other js libraries) could be recent announcements from the jQuery team about releasing mobile version of the library:
http://jquerymobile.com/ And since it will be supported by iOS and Android native browsers (among others), I think it will be really cool having Tapestry pages also being able to render jQuery components and effects on devices using those OSs. Cheers, Nikola Email: nikola.mili...@gmail.com URL: nikola.milikic.info On Wed, Aug 11, 2010 at 3:48 PM, Christophe Cordenier < christophe.corden...@gmail.com> wrote: > Hi ! > > 2010/8/11 Fritz Stelluto <fritz.stell...@ioko.com> > > > Hi there. Just my two cents as a front end dev working on Tapestry > > projects. > > > > > > I'd rather you made it easier to plug in ANY js library of one's choice, > > including purpose built ones. > > > > I think this is exactly what Howard has in mind. Factoring work has already > started in that direction. > > > > > > It should really be a day's work or so for a front end dev to decide they > > are going to use library X, find out it's not supported yet, and create a > > Tapestry bridge. Anything more involved will put people off. > > > > > > As for out-of-the-box support, even though prototype.js is one of the > worse > > libraries out there in terms of playing nice with other libraries on the > > same page, if you stop supporting it you'll have a lot of angry devs on > your > > hands, so you can't do that. > > > > If you want to offer another option to make Tapestry more palatable, > jQuery > > is the obvious option purely for its popularity. The truth of the matter > is > > that all js libraries are much of muchness (although some like ext.js are > > monster compared to others). They all get the job done. I don't think you > > should really concern yourself with that, as I said earlier, just make it > > easy to drop in any library, and we'll do the rest. For example MooTools > is > > my favourite, I'll be happy to build a bridge for that, but I don't have > the > > time nor will to tear my hair out doing it. > > > > Hope that makes sense > > > > > > Thanks > > > > Fritz > > > > > > > > > Wrt jquery vs. others, i'd say jquery has won especially for your > > > "everyday webapp", i.e. the webapp that contains lots of html > > > pages and mostly serves just that - html pages. Incidentally, i believe > > > that that's where Tapestry is good at - creating the markup for those > > > pages. > > > > > > On the other end, there's the "one-page webapps". Those mostly > > > serve data in json or xml format and I believe jquery is not well > > > suited for those (yet) - interestingly [1] was written today and deals > > > with exactly this separation. > > > > > > To get back to Tapestry though, i tried today Robin's tapestry5-jquery > > > after first upgrading it for 5.2 - see [2], [3] > > > > > > Some tests in [3] are failing but i was anxious to use it so i ported > the > > > tapestwitter app from prototype to jquery and it almost worked. > > > > > > > > > > > Both versions > > > have the exact same functionality and there's no trace of prototype in > > the > > > jquery version but there's still work to be done (zone updating in my > 5.2 > > > upgrade has some issues - but perhaps i've just messed things up) > > > > > > Anyway, almost all the changes required were about rewriting custom > > > prototype code to jquery - see [4]. So, all in all, tapestry5-jquery > > > is definitely > > > worth a try > > > > > > [1] http://rmurphey.posterous.com/on-jquery-large-applications > > > [2] http://github.com/andyhot/tapestry5-clientresources/tree/tap-5.2 > > > [3] http://github.com/andyhot/tapestry5-jquery/tree/tap-5.2 > > > [4] > > > > > > http://github.com/andyhot/tapestwitter/commit/44b5e8a49df4292eddb95499e2b234403b9c5066 > > > > > > On Mon, Aug 9, 2010 at 20:07, Ville Virtanen <ville.virta...@cerion.fi > > <mailto:ville.virta...@cerion.fi>> > > > wrote: > > > > > > > > Portlet support and this Js fix are the most important new features. > > > > Especially the no-portlet support part stopped T5 in recent > evaluation > > to > > > > build SAP front end and handling portal for multinational customer > > > running > > > > Oracle's weblogics. > > > > > > > > - Ville > > > > > > > > > > > > Howard Lewis Ship wrote: > > > >> > > > >> jQuery and Prototype have similar capabilities implemented in > > > >> extremely different ways. > > > >> > > > >> My intention is to factor out what T5 and the standard components > use > > > >> into a thin wrapper library around either Prototype or jQuery, or > > > >> others (such as Ext, YUI, etc.). Name you favorite JS library and > > > >> you'll hear people call out their favorites you've never even heard > > > >> of! > > > >> > > > >> At this point, Tapestry has had enough JS exposure for me to > identify > > > >> a minimum set of common operations. > > > >> > > > >> On Mon, Aug 9, 2010 at 9:12 AM, Pierce Wetter <pie...@paceap.com > > <mailto:pie...@paceap.com>> > > > wrote: > > > >>> > > > >>> On Aug 9, 2010, at 5:50 AM, Michael Gentry wrote: > > > >>> > > > >>>> A downside to Tapestry adopting JQuery at this point is it hurts > > those > > > >>>> of us who bit the bullet and used Prototype (since it comes with > T5 > > > >>>> for "free"). It would make upgrading more time consuming. > > > >>>> Personally, I would prefer JQuery, but there is a cost involved in > > > >>>> using it now (additional bandwidth + memory footprint) or in the > > > >>>> future (conversion). > > > >>> > > > >>> Doesn't JQuery support a superset of Prototype? Does anyone know > > what > > > >>> the incompatibilities are? > > > >>> > > > >>> > > > >> > > > >> > > > >> > > > >> -- > > > >> 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: users-unsubscr...@tapestry.apache.org > <mailto: > > users-unsubscr...@tapestry.apache.org> > > > >> For additional commands, e-mail: users-h...@tapestry.apache.org > > <mailto:users-h...@tapestry.apache.org> > > > >> > > > >> > > > >> > > > > > > > > -- > > > > View this message in context: > > > > > > http://old.nabble.com/Why-would-I-choose-JQuery--tp29360084p29390075.html > > > > Sent from the Tapestry - User mailing list archive at Nabble.com< > > http://Nabble.com>. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > <mailto: > > users-unsubscr...@tapestry.apache.org> > > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > <mailto:users-h...@tapestry.apache.org> > > > > > > > > > > > > > > > > > > > > -- > > > Andreas Andreou - andy...@apache.org<mailto:andy...@apache.org> - > > http://blog.andyhot.gr > > > Tapestry PMC / Tacos developer > > > Open Source / JEE Consulting > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org<mailto: > > users-unsubscr...@tapestry.apache.org> > > > For additional commands, e-mail: users-h...@tapestry.apache.org > <mailto: > > users-h...@tapestry.apache.org> > > > > > > > > > > > > > > > > > > Cheers > > Fritz > > -- > > Fritz Stelluto > > +44 (0)7817 719 566 / fritz.stell...@ioko.com<mailto: > > fritz.stell...@ioko.com> / fritzthe...@gmail.com<mailto: > > fritzthe...@gmail.com> > > > > ioko > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > -- > Regards, > Christophe Cordenier. > > Committer on Apache Tapestry 5 > Co-creator of wooki @wookicentral.com >
