[
https://issues.apache.org/jira/browse/TAPESTRY-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1373.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.5
It's not precisely the same as T4's Palette ... it's actually a lot better. It
keeps the available items in natural order (as defined by the SelectModel) and
keeps the selected list in natural order if reordering is not enabled. Better,
cleaner JavaScript and it generates a real minimum of JS on the page (just an
object instantiation, everything else is in a reusable library).
T4 had the idea of keeping the items sorted by label (the visible value) or
value (the invisible value). Keeping them in SelectModel-defined order just
makes much more sense.
> Recreate T4's Palette component for T5
> --------------------------------------
>
> Key: TAPESTRY-1373
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1373
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.5
>
>
> A good multi-selection (and optionally, ordering) component is essential,
> especially as we try to implement some Trails-like behavior on top of
> Hibernate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
