There is no obligation to use UIItemRendererBase for Jewel ItemRenderers. If you run into places where we assume UIItemRendererBase and not IItemRenderer, that's either a bug or requires a different controller or view.
Let us know what you run into. -Alex On 4/14/18, 8:33 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote: >Hi, > >this base class > >UIItemRendererBase > >has properties for all colors (hover, selected, and more) and a "useColor" >property, and updateRenderer() method is switching "useColor" > >as a low level class, I think this class should not have all this info, >since most people will never use. > >In Basic I think is possible, but in Jewel colors, shapes and effects >comer >from CSS. > >In this case I think 95% of users will never go that way of setting colors >when the can do simply this: > >.jewel.item { >cursor: pointer; >padding: 8px; >flex-shrink: 0; >flex-grow: 1; >} >.jewel.item:hover { >color: #FFFFFF; >background: #24a3ef; >} >.jewel.item:active, .jewel.item.selected { >color: #FFFFFF; >background: #0f88d1; >} > >without wiring a single line between logic and css. > >So I think useColors, and colors should be refactored to a bead or >something that will not compromise the high level UI sets that will never >use this kind of properties. > >Although I'm creating a ItemRenderer from scratch, my problem here's that >there's so much hierarchy here and many other classes in the tree that >depends. > >Creating a class extending "leaf" class nodes are easy, but when problems >arise in the middle of the hierarchy chain, we have a problem that is >difficult to solve > >thanks > > > >-- >Carlos Rovira >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2 >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6594b31e04554af2d97808d5 >a21d2617%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636593168509138978&s >data=q1GZeXydbyaKPui4RFXJG4%2FlUdCrTcioiycbxGE5FD4%3D&reserved=0
