tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Adams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-486) Switch Tapestry's built-in JavaScript support from Prototype to jQuery
Date Fri, 30 Jan 2009 18:34:59 GMT

    [ https://issues.apache.org/jira/browse/TAP5-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668970#action_12668970
] 

Dan Adams commented on TAP5-486:
--------------------------------

It may be worth noting that my objection has nothing to do with whether or not I like jquery.
I actually like it quite a bit. :)

> 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.


Mime
View raw message