[
https://issues.apache.org/jira/browse/TAPESTRY-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570622#action_12570622
]
Francois Armand commented on TAPESTRY-2179:
-------------------------------------------
There was several threads on the mailing about this topic, one of them being :
http://www.nabble.com/Prototype-vs.-JQuery-vs.-Dojo-0.9-vs.-----tt13011440.html#a13011440
The isolation layer / adapter approach is a recurrent pattern in most of them.
There is also an open about "Tracking issue for Ajax support" that may be
linked to this issue : https://issues.apache.org/jira/browse/TAPESTRY-1650
> Javascript Adapter Architecture
> -------------------------------
>
> Key: TAPESTRY-2179
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2179
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components
> Affects Versions: 5.0.10
> Reporter: Christian Gorbach
> Priority: Minor
> Fix For: 5.0.11
>
>
> Almost every aspect in T5 can be easily overridden or decorated - except the
> client side javascript code.
> A lightweight javascript isolation layer would allow people to swap the
> javascript frameworks.
> http://extjs.com/ uses this approach (can be driven by own, prototype,
> jquery, etc..) and it works well.
> The isolation level layer should respect javascript programming patterns
> (module pattern, keep the DOM clean,..). This would allow T5 to smoothly
> integrate in existing (corporate) environments.
> See Discussion on Howards blog:
> http://tapestryjava.blogspot.com/2008/02/prototype-and-custom-events.html
> Javascript patterns:
> http://klauskomenda.com/code/javascript-programming-patterns/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
