Maybe [Embed] could store bitmaps and binary data as Data URIs on the JS side:
https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Using_images#Embedding_an_image_via_data_URL https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs - Josh On Mon, Mar 6, 2017 at 9:05 AM, Harbs <harbs.li...@gmail.com> wrote: > How to add full support for [Embed] is a complicated question. > > I think it would be great to support it, but the details get sticky. I > think we need a list of use cases for [Embed] to figure out the right > behavior for each and a way to differentiate the use cases. On the simplest > level, it could simply copy files and set src to the copied path. Maybe get > fancy with BinaryData? What to do with BitmapData? What about Class > assignment? I’m not sure what the right answer is to these questions. > > For the BlendBead, all we really need though, is SWF support. The JS side > does not rely on the PixelBender files. > > Harbs > > > On Mar 6, 2017, at 6:54 PM, Alex Harui <aha...@adobe.com> wrote: > > > > > > > > On 3/6/17, 8:33 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > > >> Yishay got an error that ByteArrayAsset could not be found. > > > > Ah yes. That should be relatively easy to fix for SWF compiles. But > > what should the cross-compiler do? > > > > -Alex > > > >
