Makes sense. I was wondering mainly about some emulation to keep the syntax. It looks like the compiler is trying to do something with these declarations, but it could be unintended.
From: Andrew Wetmore<mailto:[email protected]> Sent: Wednesday, February 26, 2020 3:30 PM To: Apache Royale Development<mailto:[email protected]> Subject: Re: Embed in Royale I don't believe Embed is required or would be a benefit in Royale, if you are going to compile an app to run on a browser using JavaScript. This page [1] on Flex equivalents says "Embedding assets was necessary in Flex so the application could quickly access images and other assets that were part of a compiled Flash SWF. To make it easy to display on a button an icon that was in a SWF, we wrote something like: <mx:Button icon="@Embed('icons.swf#our_button')"/> Since JavaScript does not support the concept of embedding assets, doing the same thing in Royale is a simple URL reference: <mx:Button icon="icons/our_button.png"/> (once you have placed the relevant image in the *icons* folder). [1] https://apache.github.io/royale-docs/migrate-an-existing-app/flex-equivalents On Wed, Feb 26, 2020 at 9:18 AM Yishay Weiss <[email protected]> wrote: > Does Embed work in Royale? > > I’m working on a POC to port an app that has some css that looks like [1] > this, but the compiler complains with messages such as > > [mxmlc] Error: The definition of base class BitmapAsset was not found. > > Which makes sense as BitmapAsset does not exist in Royale src. > > Am I right in assuming that this is not yet implemented? > > Thanks. > > [1] > .closeBtn { > upSkin: Embed('/assets/16x16/button_cancel.png'); > overSkin: Embed('/assets/16x16/button_cancel.png'); > downSkin: Embed('/assets/16x16/button_cancel.png'); > disabledSkin: Embed('/assets/16x16/button_cancel.png'); > } > -- Andrew Wetmore http://cottage14.blogspot.com/
