[ https://issues.apache.org/jira/browse/TAP5-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058164#comment-13058164 ]
Hudson commented on TAP5-999: ----------------------------- Integrated in tapestry-trunk-freestyle #400 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/400/]) TAP5-999: Introduce empty SPI (service provider interface) and prototype adapter layers TAP5-999: Add a function for extracting a named property from the elements of an array hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1141760 Files : * /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-spi.js * /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/javascript/CoreJavaScriptStack.java * /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-prototype.js hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1141759 Files : * /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-arrays.js * /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/JavaScriptTests.tml > Implement an agnostic tapestry.js layer + adapters to allow developers to > switch from prototype to jquery > --------------------------------------------------------------------------------------------------------- > > Key: TAP5-999 > URL: https://issues.apache.org/jira/browse/TAP5-999 > Project: Tapestry 5 > Issue Type: Wish > Components: tapestry-core > Affects Versions: 5.1.0.7, 5.0.19 > Reporter: Christophe Cordenier > Assignee: Howard M. Lewis Ship > > As per the discussion on the mailing about Tapestry 5 and jQuery, i create > this JIRA to compile the toughts of everyone for this feature. > As Howard said on the mailing list, goals are : > Goal #1: Backwards compatibility > Goal #2: Documented > Goal #3: Plugability / Extensibility / Overridablilty > First design thoughts suggested by howard are (extracted from Howard's > answer) : > 1. tapestry.js defines a Tapestry namespace with key function properties for > the standard stuff > 2. split current tapestry.js into more smaller files > 3. In addition to tapestry.js, ... include either > tapestry-prototype-adapter.js (plus prototype.js and scriptaculous.js) OR > tapestry-jquery-adapter.js (plus jquery.js). > 4. tapestry.js [should] be smaller handlers that often just fire additional > events; a cascade of events that eventually results in server-side requests > Objectives : > 1. make certain parts more pluggable i.e. Popup Bubbles > 2. write javascript with functional closures > 3. ... element could have at most one active animation; the animation would > have to complete before the next one (cf. jQuery animation and queuing > mechanism) > Challenges : > 1. Remove prototype code from tapestry.js > 2. Keep backward compatibility with existing Tapestry object -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira