You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by iberck <ib...@gmail.com> on 2010/10/27 21:30:16 UTC
Re: jQuery Integration for 5.2
Here there are more reasons to create the base components with jquery
46% of the applications on the web are made in jquery
http://trends.builtwith.com/javascript/JQuery
Regards
--
View this message in context: http://tapestry.1045711.n5.nabble.com/jQuery-Integration-for-5-2-tp2834002p3239343.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: jQuery Integration for 5.2
Posted by iberck <ib...@gmail.com>.
Thank you for your time and your response
more or less on what time we will have that javascript stacks ?
Thanks in advance
--
View this message in context: http://tapestry.1045711.n5.nabble.com/jQuery-Integration-for-5-2-tp2834002p3239781.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: jQuery Integration for 5.2
Posted by Inge Solvoll <in...@gmail.com>.
Couldn't you just decorate the CoreJavaScriptStack?
2010/10/31 françois facon <fr...@gmail.com>
> thanks for the link.
>
> but even if you use jquery with the no conflit mode with prototype,
> you must include jquery.js before prototype.
>
> see
>
> http://stackoverflow.com/questions/2830510/jquery-noconflict-not-working-in-ie8-only
>
>
> is it to late (for 5.2) to propose evolution on CoreJavascriptStack
> for
> - adding prototype only if it's needed
> - set the order of core stack when using more than one toolkit ( jquery
> before prototype)
> - add core stack required when needed by a component (kind of @ImportCore)
>
Re: jQuery Integration for 5.2
Posted by françois facon <fr...@gmail.com>.
thanks for the link.
but even if you use jquery with the no conflit mode with prototype,
you must include jquery.js before prototype.
see
http://stackoverflow.com/questions/2830510/jquery-noconflict-not-working-in-ie8-only
is it to late (for 5.2) to propose evolution on CoreJavascriptStack
for
- adding prototype only if it's needed
- set the order of core stack when using more than one toolkit ( jquery
before prototype)
- add core stack required when needed by a component (kind of @ImportCore)
Re: jQuery Integration for 5.2
Posted by ael <al...@dash.com.ph>.
http://docs.jquery.com/Using_jQuery_with_Other_Libraries
http://docs.jquery.com/Using_jQuery_with_Other_Libraries
--
View this message in context: http://tapestry.1045711.n5.nabble.com/jQuery-Integration-for-5-2-tp2834002p3241521.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: jQuery Integration for 5.2
Posted by françois facon <fr...@gmail.com>.
In got5, we miss the backward compatibility issue with project that use lot
of prototype.
In other hand, what is the use of importing prototype, when it's not
needed.
As far as i can see in 5.2 CoreJavascriptStack, will be in charge of adding
core part of js toolkit.
So what would be the best way, to contribute to this core stack?
for me it would be nice to
- add prototype only if it's needed
- set the order of core stack when using more than one toolkit ( jquery
before prototype)
- add core stack required when needed by a component (kind of @ImportCore)
2010/10/27 Thiago H. de Paula Figueiredo <th...@gmail.com>
> On Wed, 27 Oct 2010 17:30:16 -0200, iberck <ib...@gmail.com> wrote:
>
> Here there are more reasons to create the base components with jquery
>> 46% of the applications on the web are made in jquery
>> http://trends.builtwith.com/javascript/JQuery
>>
>
> It's not just a matter of replacing Prototype with jQuery. Most of the
> Tapestry apps and third-party packages built until use Prototype for their
> JavaScript and backward compatibility is something very important to the
> project. The JavaScript stacks is part of the solution to this problem.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: jQuery Integration for 5.2
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Wed, 27 Oct 2010 17:30:16 -0200, iberck <ib...@gmail.com> wrote:
> Here there are more reasons to create the base components with jquery
> 46% of the applications on the web are made in jquery
> http://trends.builtwith.com/javascript/JQuery
It's not just a matter of replacing Prototype with jQuery. Most of the
Tapestry apps and third-party packages built until use Prototype for their
JavaScript and backward compatibility is something very important to the
project. The JavaScript stacks is part of the solution to this problem.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org