[ http://issues.apache.org/jira/browse/ADFFACES-248?page=all ]
Pavitra Subramaniam updated ADFFACES-248:
-----------------------------------------
Attachment: Patch248+244.patch
The earlier patch for this issue (248) produced too many conflicts when applied
on top of patch 244 (which was commited by Gab) as both are related to the same
component.
So I created a new patch on latest Trinidad that includes the commits for issue
244.
> Propose adding a 'visited' attribute to the commandNavigationItem component...
> ------------------------------------------------------------------------------
>
> Key: ADFFACES-248
> URL: http://issues.apache.org/jira/browse/ADFFACES-248
> Project: MyFaces ADF-Faces
> Issue Type: New Feature
> Reporter: Pavitra Subramaniam
> Assigned To: Simon Lessard
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
