tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1113) Palette client side instanciation should be done using Tapestry.initializer
Date Mon, 04 Nov 2013 23:04:17 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-1113.
--------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

This is no longer relevant due to significant changes in place in Tapestry 5.4.

> 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
>            Reporter: Robin Komiwes
>            Assignee: Howard M. Lewis Ship
>            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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message