Place for further notes: https://github.com/apache/royale-asjs/wiki/css-class-utility-component-set
Andrew Wetmore Assistant VP, Marketing and Publicity, The ASF <https://apache.org> Editor-Writer, Infra team, The ASF Editor, moosehousepress.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Feb 17, 2026 at 1:22 PM Josh Tynjala <[email protected]> wrote: > Makes sense to me! > > -- > Josh Tynjala > Bowler Hat LLC > https://bowlerhat.dev/ > > > On Tue, Feb 17, 2026 at 9:17 AM Harbs <[email protected]> wrote: > > > I want to start working on a component set which has css-class utility > > functionality built in. > > > > Royale has a StyledUIBase class which was created to support Jewel, but > it > > lives in Basic in the org.apache.royale.core package. > > > > The assumptions made in that class are very specific to the inner > workings > > of Jewel and my opinion is that’s where it belongs. > > > > The fact that it lives in core makes creating an alternate approach > > difficult. > > > > I would like to move the following classes to the Jewel project under the > > org.apache.royale.jewel path: > > > > IStyledUIBase > > StyledUIBase > > StyledImageBase > > StyledUIItemRendererBase > > > > This will also effect > > > > - MediaElement in HTML5 > > - FontIconBase in Icons > > > > Those two classes should be easy to resolve. > > > > I don’t think moving it to Jewel will effect anything else unless there > > are people using those classes directly anywhere. > > > > Does anyone have objections to this change? > > > > Thanks, > > Harbs >
