You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/06/29 03:34:28 UTC
[jira] [Commented] (TAP5-999) Implement an agnostic tapestry.js
layer + adapters to allow developers to switch from prototype to jquery
[ https://issues.apache.org/jira/browse/TAP5-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056941#comment-13056941 ]
Hudson commented on TAP5-999:
-----------------------------
Integrated in tapestry-trunk-freestyle #394 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/394/])
TAP5-999: Fill in more unit tests for client-side JavaScript functions
TAP5-999: Rewrite the JS unit testing script to use simple <DIV> elements, not a complex table
TAP5-999: Add tests for T5.arrays.is(Non)Empty
TAP5-999: Make more use of nested namespaces under T5
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1140922
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/JavaScriptTests.tml
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1140918
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/js-testing.css
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/JavaScriptTests.tml
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/js-testing.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/groovy/org/apache/tapestry5/integration/app1/TapestryJavaScriptTests.groovy
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1140917
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/JavaScriptTests.tml
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1140916
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-init.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-core.js
* /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
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-pubsub.js
> 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