On 11/13/13 1:33 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > >The usecase here is that there are n Lists (for each column) composed by >the DataGrid component. If the users rollsover an on any list, the >corresponding itemrenderers in each column must highlight themselves. So, >keeping track of the current rollOverIndex as part of DataGrid's model is >a >must. > >After reading your comments multiple times, here is one approach we could >do.
I guess I'm not understanding why you want to combine the rollovermodel with the main model. You are certainly allowed to do so in order to "inline" something for speed, but IMO, it is important to make sure that you have the right separation of concerns which means that a set of beads that implements rollover can be added or removed as a set and everything else keeps working. Theoretically, you should be able to set up media queries such that when this app gets loaded in an Android browser it never loads the rollover implementation. You don't always get to re-compile for the target. In my mind, the rolloverindex isn't part of the API surface of the component. It should be ok to have a separate rollovermodel and hang it on the strand and have an implementation bead find it via getBeadByType. But of course, I could be wrong. I think this is a useful discussion. Thanks, -Alex
