wnside 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.
> &g
olved in
> > >>>> using it now (additional bandwidth + memory footprint) or in the
> > >>>> future (conversion).
> > >>>
> > >>> Doesn't JQuery support a superset of Prototy
;> --
> >> 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!
> >>
> >
bandwidth + memory footprint) or in the
> >>>> future (conversion).
> >>>
> >>> Doesn't JQuery support a superset of Prototype? Does anyone know what
> >>> the incompatibilities are?
> >>>
> >>>
> >>
> >>
> >>
> &g
-
>> 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:
>
> (971) 678-5210
> http://howardlewisship.com
>
> -------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional command
have all the latest
> bells and whistles. Of ready-made components, only a good, skinnable,
> customizable and extensible tab component is relevant to me. Now, why
> would I choose JQuery over the other choices? I'd really love to hear
> comments from p
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
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 th
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
and for JQuery. It might be
>>>>> marginally easier to adjust the existing Javascript for Dojo than
>>>>> having to rewrite everything with JQuery but as said, I'm fine with
>>>>> the cost. P
nd for JQuery. It might be
> > >> marginally easier to adjust the existing Javascript for Dojo than
> > >> having to rewrite everything with JQuery but as said, I'm fine with
> > >> the cost. Performance always matters, so load times, execution
> > >&
tter. I don't mind filing
> >> an occasional issue, but I don't want to get sucked into seriously
> >> having to debug and maintain another add-on library so I'd prefer
> >> something relatively stable even if it didn't have all the latest
> >&
l issue, but I don't want to get sucked into seriously
>> having to debug and maintain another add-on library so I'd prefer
>> something relatively stable even if it didn't have all the latest
>> bells and whistles. Of ready-made components, only a good, skin
x27;t want to get sucked into seriously
> having to debug and maintain another add-on library so I'd prefer
> something relatively stable even if it didn't have all the latest
> bells and whistles. Of ready-made components, only a good, skinnable,
> customizable and extensibl
et sucked into seriously
having to debug and maintain another add-on library so I'd prefer
something relatively stable even if it didn't have all the latest
bells and whistles. Of ready-made components, only a good, skinnable,
customizable and extensible tab component is relevant to me. Now,
16 matches
Mail list logo
