flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FlexJS] Embed Workaround
Date Mon, 06 Mar 2017 19:35:14 GMT
I just pushed an untested attempt to allow using a different class for
embeds.  It is in the develop branch.

Normally, the compiler expects to find a flex SDK swc with
mx.core.ByteArrayAsset in it.  You should be able to create an
org.apache.flex.core.ByteArrayAsset class that extends
flash.utils.ByteArray and add the compiler option
-compiler.byte-array-embed-class=org.apache.flex.core.ByteArrayAsset.  I
don't think the IFlexAsset interface is required.

HTH,
-Alex

On 3/6/17, 9:32 AM, "Harbs" <harbs.lists@gmail.com> wrote:

>I’m sorry but you totally lost me there… ;-)
>
>What name, used where?
>
>I don’t understand how the [Embed] tag works and where the ByteArrayAsset
>comes from.
>
>> On Mar 6, 2017, at 7:27 PM, Alex Harui <aharui@adobe.com> wrote:
>> 
>> 
>> 
>> On 3/6/17, 9:05 AM, "Harbs" <harbs.lists@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.
>> 
>> Well, in keeping with other compiler changes, the answer would be to
>>make
>> the name of the ByteArrayAsset class configurable like we did for the
>> PropertyChangeEvent.  If you want a quick fix for now, just change the
>> name used in DataTranscoder.java.
>> 
>> Thanks,
>> -Alex
>> 
>

Mime
View raw message