[
https://issues.apache.org/jira/browse/TAP5-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669197#action_12669197
]
Joost Schouten commented on TAP5-486:
-------------------------------------
A switch would mean a lot of work on a few project for me too. So a switch
would not get my vote. One thing that I would find interesting is to change the
tapestry.js, and some of the other included *.js files into an thin interface
like wrapper that does not rely on any framework. Then pull out all javascript
into a seperate module and contribute the javascript module of your choice.
This way nothing needs to change from the way it currently works with prototype
(assuming prototype as the default), but it does allow to "plug in" any other
framework, like jQuery or MooTools. Martin Reurings actually proposed a
similair solution back in 2007
http://mail-archives.apache.org/mod_mbox/tapestry-dev/200710.mbox/%3cof6624565c.dad9ba14-onc1257369.00426459-c1257369.00440...@porsche.co.at%3e
Cheers,
Joost
> Switch Tapestry's built-in JavaScript support from Prototype to jQuery
> ----------------------------------------------------------------------
>
> Key: TAP5-486
> URL: https://issues.apache.org/jira/browse/TAP5-486
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
>
> Like rats deserting a sinking ship ...
> This is not a definitive requirement; I've created this issue to promote
> discussion.
> It's quite likely that a move like this could be accomplished quite smoothly
> for users who are meerly consumers of JavaScript components; authors of
> JavaScript components would have to make some changes.
> Possibly we should code the jQuery stack from the get-go to NOT use the $()
> method, but instead use j$(). That extra character to type could make all the
> difference is allowing a smooth upgrade, where jQuery becomes the default,
> but prototype/scriptaculous can still be used.
> Possibly a new annotation, @PrototypeSupport for components to ensure that
> the Prototype libraries are available for compatibility?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
