You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/05/11 04:01:47 UTC
[jira] [Created] (TAP5-1521) JavaScriptSupport.addInitializerCall()
should support JSONArray of function parameters, as RenderSupport does
JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
-------------------------------------------------------------------------------------------------------------
Key: TAP5-1521
URL: https://issues.apache.org/jira/browse/TAP5-1521
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.5, 5.3.0
Reporter: Howard M. Lewis Ship
JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1521) JavaScriptSupport.addInitializerCall()
should support JSONArray of function parameters, as RenderSupport does
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1521.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3.0
>
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1521)
JavaScriptSupport.addInitializerCall() should support JSONArray of function
parameters, as RenderSupport does
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1521:
------------------------------------------
Assignee: Howard M. Lewis Ship
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1521)
JavaScriptSupport.addInitializerCall() should support JSONArray of function
parameters, as RenderSupport does
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072626#comment-13072626 ]
Hudson commented on TAP5-1521:
------------------------------
Integrated in tapestry-trunk-freestyle #441 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/441/])
TAP5-1521: Add test for basic traditional (non-Ajax) alerts
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1152050
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/groovy/org/apache/tapestry5/integration/app1/AlertsTests.groovy
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1521)
JavaScriptSupport.addInitializerCall() should support JSONArray of function
parameters, as RenderSupport does
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072626#comment-13072626 ]
Hudson commented on TAP5-1521:
------------------------------
Integrated in tapestry-trunk-freestyle #441 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/441/])
TAP5-1521: Add test for basic traditional (non-Ajax) alerts
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1152050
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/groovy/org/apache/tapestry5/integration/app1/AlertsTests.groovy
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1521)
JavaScriptSupport.addInitializerCall() should support JSONArray of function
parameters, as RenderSupport does
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1521:
------------------------------------------
Assignee: Howard M. Lewis Ship
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1521) JavaScriptSupport.addInitializerCall()
should support JSONArray of function parameters, as RenderSupport does
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1521.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1521
> URL: https://issues.apache.org/jira/browse/TAP5-1521
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3.0
>
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well. Therefore, it should be re-implemented efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in a very inefficient way. Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira