Pavitra Subramaniam wrote:
Comments below
- Pavitra
- Whatever we decide to do about the autobind or rowData interface is ok with me.
- But I believe that the train component should not be bound to a MenuModel for various reasons. One a train is not a menu.
The name menuModel should have been changed, but there is nothing menu
specific about it.
Two, there are cases (internally @ Oracle) where people want to define train metadata using structures, other than MenuModel & that has information that can help determine, say, the visited state of a stop.
Can you explain
1] What this new api you are proposing looks like?
2] How this is better than writing a menuModel implementation with their
data?
Thanks,
Gab
