[
https://issues.apache.org/jira/browse/ADFFACES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated ADFFACES-248:
----------------------------------------
Fix Version/s: 1.0.0-incubating-core
Affects Version/s: 1.0.0-incubating-core
> Propose adding a 'visited' attribute to the commandNavigationItem component...
> ------------------------------------------------------------------------------
>
> Key: ADFFACES-248
> URL: https://issues.apache.org/jira/browse/ADFFACES-248
> Project: MyFaces ADF-Faces
> Issue Type: New Feature
> Affects Versions: 1.0.0-incubating-core
> Reporter: Pavitra Subramaniam
> Assigned To: Gabrielle Crawford
> Fix For: 1.0.0-incubating-core
>
> Attachments: Issue-248.patch, Patch248+244.patch
>
>
> I would like to propose adding a 'visited' attribute to the
> commandNavigationItem component.
> This attribute is relevant only when used within the train component. We
> currently have an inaccurate way of figuring out if a stop has been visited
> or not. The renderer gets the row index of the currently active node and
> marks every node with an index <= current rowIndex, as 'visited'.
> There are many flaws with this approach
> - for one it assumes that stops are ordered (iow, they have a sequential
> flow).
> - secondly, the renderer assumes a behavior for the train when it should let
> the model drive this behavior. For instance, I need to support a use case,
> where the train stops are all enabled by default and user can jump to any
> stop. In such situations the above algorithm fails.
> A 'visited' API on the component allows the model to set the visited state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
