You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Robin Komiwes (JIRA)" <ji...@apache.org> on 2010/04/21 16:07:50 UTC
[jira] Created: (TAP5-1113) Palette client side instanciation
should be done using Tapestry.initializer
Palette client side instanciation should be done using Tapestry.initializer
---------------------------------------------------------------------------
Key: TAP5-1113
URL: https://issues.apache.org/jira/browse/TAP5-1113
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Robin Komiwes
Priority: Minor
Actually Palette component is initalized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done using :
renderSupport.addInit(...);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1113) Palette client side instanciation
should be done using Tapestry.initializer
Posted by "Robin Komiwes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robin Komiwes updated TAP5-1113:
--------------------------------
Description:
Actually Palette component is initialized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done using :
renderSupport.addInit(...);
was:
Actually Palette component is initalized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done using :
renderSupport.addInit(...);
> Palette client side instanciation should be done using Tapestry.initializer
> ---------------------------------------------------------------------------
>
> Key: TAP5-1113
> URL: https://issues.apache.org/jira/browse/TAP5-1113
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Robin Komiwes
> Priority: Minor
>
> Actually Palette component is initialized using this portion of code:
> renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
> In order to be less dependent from a particular JS framework, it should be done using :
> renderSupport.addInit(...);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1113) Palette client side instanciation
should be done using Tapestry.initializer
Posted by "Robin Komiwes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robin Komiwes updated TAP5-1113:
--------------------------------
Description:
Actually Palette component is initialized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done using :
renderSupport.addInit(...);
was:
Actually Palette component is initalized using this portion of code:
renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
In order to be less dependent from a particular JS framework, it should be done using :
renderSupport.addInit(...);
> Palette client side instanciation should be done using Tapestry.initializer
> ---------------------------------------------------------------------------
>
> Key: TAP5-1113
> URL: https://issues.apache.org/jira/browse/TAP5-1113
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Robin Komiwes
> Priority: Minor
>
> Actually Palette component is initialized using this portion of code:
> renderSupport.addScript("new Tapestry.Palette('%s', %s, %s);", clientId, reorder, naturalOrder);
> In order to be less dependent from a particular JS framework, it should be done using :
> renderSupport.addInit(...);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.