Type Selectors are pruned out if the Class/Type is not used in the output. I've toyed with ways to prune class selectors. If you use class selectors with names with the pattern:
opt_class-qualified-name-with-hyphens_SomeName Then the compiler will prune out the class selector if that class is not in the output. That way you can associate class selectors with a class. Another option is to not use class selectors at all in the framework. Create subclasses for all of the internal pieces and create type selectors for them. This also avoids using advanced selectors in the CSS Implementation. HTH, -Alex On 4/9/18, 11:56 PM, "Harbs" <harbs.li...@gmail.com> wrote: >We can probably eliminate the vast majority of code redundancy if that’s >true. The problem with CSS is that it’s pretty hard to do the same there. > >Is there any way to strip the css down to only the classes that are >actually used by the components used in the app? I’m guessing that will >be really hard… > >The work you’ve done with Jewel is great, but I didn’t realize this >down-side of using css classes until now. > >Harbs > >> On Apr 10, 2018, at 9:45 AM, Carlos Rovira <carlosrov...@apache.org> >>wrote: >> >> @Harbs, one more thing I forgot to say before, you must notice is that >> Jewel will increase a bit in size in CSS since I'll try layouts to be >> mostly CSS rules, in the other hand that will sabe lots of redundant >>inline >> code in HTML setting margins, displays, paddings, and more. >
