[ https://issues.apache.org/jira/browse/TAP5-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674864#action_12674864 ]
luna Guo commented on TAP5-486: ------------------------------- jQuery has thousands of plugins that i can use them easily without much javascript experience.I can't leave it .Even i've written some code using prototype,i have to include jQuery for using a lot of UI components.There's hundreds kb of javascript for a page. I think the javascript lib tapestry include must be small and a lot of UI can be find.I like jQuery's "Write Less, Do More". To use a small one,and never change it to another again.We don't want to lean/use so many javascript frameworks. > 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.