Between us, you’re the writer… ;-)


> On Feb 19, 2026, at 5:21 PM, Andrew Wetmore <[email protected]> wrote:
> 
> We have a blog that is covered with cobwebs. This seems like the sort of
> thing I should write a blog entry about. Unless you would like to write
> it...
> 
> a
> 
> Andrew Wetmore
> Assistant VP, Marketing and Publicity, The ASF <https://apache.org 
> <https://apache.org/>>
> Editor-Writer, Infra team, The ASF
> 
> Editor, moosehousepress.com <http://moosehousepress.com/>
> 
> 
> On Thu, Feb 19, 2026 at 11:07 AM Harbs <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>> Just a couple of notes on this:
>> 
>> StyledUIBase and all of the associated files have been moved to
>> org.apache.royale.jewel.
>> 
>> As long as clients are not referencing any of these classes directly,
>> things should work without modification.
>> If there are references in projects, there will be a need to adjust the
>> imports to point to the correct paths.
>> 
>> Besides Jewel, the following were touched by this:
>> 
>> MediaElement and the subclasses of VideoElement and AudioElement in HTML5.
>> 
>> My assumption is that the only clients of these classes were using Jewel —
>> or at least the StyledUIBase aspects of them.
>> 
>> I created a second MediaElement class in the org.apache.royale.jewel
>> package which is based on StyledUIBase and reverted the HTML5 one to be
>> based on UIBase.
>> 
>> Jewel VideoPlayer and AudioPlayer now subclass the new MediaElement in
>> Jewel.
>> 
>> The other class using StyledUIBase was FontIconBase in the Icon project.
>> 
>> I added an implementation of addClass, removeClass and toggleClass in
>> there to preserve that existing interface.
>> 
>> If anyone using these classes have any issues, please let me know ASAP so
>> I can fix things.
>> 
>> Thanks,
>> Harbs
>> 
>> 
>>> 
>> 
>> 
>> 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.www.avast.com <http://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>

Reply via email to