Tapestry 5
  1. Tapestry 5
  2. TAP5-486

Switch Tapestry's built-in JavaScript support from Prototype to jQuery


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s:
    • Fix Version/s: None
    • Component/s: tapestry-core
    • Labels:


      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?


        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Comment [ There's no rationale for having Java developers dictating what Javascript framework front end developers should be using. Surely the way forward is to decouple the two to allow developers to plug in ANY framework they want into Tapestry.

        Prototype is not the best framework out there. I suspect Java developers only picked Prototype because it uses the word 'Class' which give them a warm fuzzy feeling. ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Howard M. Lewis Ship [ hlship ]
        Resolution Duplicate [ 3 ]


          • Assignee:
            Howard M. Lewis Ship
            Howard M. Lewis Ship
          • Votes:
            22 Vote for this issue
            21 Start watching this issue


            • Created: