Well if it were up to me, the Basic List and SimpleList will only support the dataprovider/factory mechanism and not support setting random children. Again, I am trying to make sure the Basic set does not have just-in-case code. I think you've added components that thinly wrap HTML elements so I would suggest we add UL and OL components that would extend Container. We could also have more Flex-like names for UL and OL like UnorderedListContainer and OrderedListContainer.
So, for MDL, my thinking would center around what your target users expect. Will they be surprised or annoyed to have to learn about data providers in order to make a list? Would they expect to find an LI component? If so, then instead of extending HTML List or SimpleList, you may just want to extend Container. Thoughts? -Alex On 11/22/16, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote: >> Ugh. SimpleList got ruined in the back port from JS to AS. >> >> >So maybe I should wait for some fix on this component? > > >> It occurred to me though that both SimpleList and List/ListBase are >>going >> to be oriented towards the "ItemRenderer Factory" API. In such a case, >> there is a dataProvider and for List you specify a template (an >> ItemRenderer) and a factory and the children are generated by the >>factory. >> For MDL, do you want to do the same thing or make it more like generic >> HTML lists where you have to explicitly specify each child. IMO, a >> generic HTML List of ul/li tags essentially means there is no template. >> The contents of each li tag can have a completely different structure. >> >> Thoughts? >> -Alex >> >> >I think List should support both, a dataProvider that gives data and you >could have an factory >that created one kind of item renderers or more that one (in old flex sdk >we could have one item renderer in different rows (and in data grid by >cell) > >If you check the MDL List example page here: >https://getmdl.io/components/index.html#lists-section >you could see this structure: > ><ul class='mdl-list'> <li class="mdl-list__item"> <span class=" >mdl-list__item-primary-content"></span> </li> <li class="mdl-list__item"> >< >span class="mdl-list__item-primary-content"></span> </li> <li class=" >mdl-list__item"> <span class="mdl-list__item-primary-content"></span> ></li> ></ul> > >So I think the List should provide the ul and has an the user should >create >his own item renderer with provided pieces (more common) and his own made >pieces. > > > >-- >Carlos Rovira >http://about.me/carlosrovira
