Yes, we’ll probably switch to Jewel DataGrid long term. From: Carlos Rovira<mailto:[email protected]> Sent: Monday, December 23, 2019 7:29 PM To: [email protected]<mailto:[email protected]> Subject: Re: Smart Selectors for Beads Something that leaves me uneasy is the use of the Jewel Table component
El lun., 23 dic. 2019 a las 16:37, Alex Harui (<[email protected]>) escribió: > If the objects can all subclass a base class then you can use one of our > fake type selectors. > > Alternatively, and I don't think we've tried this, but all interested > classes could load a bead that injects an additional classname/typename and > then the descendant CSS can use that instead of .datechooser. > > That said, it isn't clear to me why your descendant selector didn't work > so there might be a bug there. I don't know if SimpleCSSValuesImpl handles > descendant selectors. Cuz it is 'Simple' > > -Alex > > On 12/23/19, 7:22 AM, "Yishay Weiss" <[email protected]> wrote: > > I need to add a bead to all Table objects in our application, but not > to Table objects contained within another specific css class. So in our css > I’ve defined > > j|Table { > IBeadView: ClassReference("classes.beads.GridLikeTableView"); > } > > But now I find that tables in a calendar are also affected, which is > unintended. So I tried adding before that > > .datechooser j|Table { > IBeadView: > ClassReference("org.apache.royale.jewel.beads.views.TableView"); > } > > But that affects all Table objects whether or not they’re contained in > a .datachooser class. Any ideas how to be more surgical about adding beads? > > > -- Carlos Rovira http://about.me/carlosrovira
