IImageModel should perhaps define the getter/setter for sources as:
function get source():Object;
function set source(value:Object):void;
instead of:
function get source():String;
function set source(value:String):void;
In the Flash based implementation, we need to have the option of setting a
On 9/11/13 11:08 AM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Wed, Sep 11, 2013 at 10:58 AM, Alex Harui aha...@adobe.com wrote:
Maybe, or in FlexJS, where we don't try to make a one-size-fits-all
component, there will be a separate component called EmbeddedImage.
I had a usecase
Maybe, or in FlexJS, where we don't try to make a one-size-fits-all
component, there will be a separate component called EmbeddedImage. FWIW,
most usage of embedded images in Flex via Image/SWFLoader was a waste of
memory. A much lighterweight class is possible. For FlexJS, embedded
images on
On Wed, Sep 11, 2013 at 10:58 AM, Alex Harui aha...@adobe.com wrote:
Maybe, or in FlexJS, where we don't try to make a one-size-fits-all
component, there will be a separate component called EmbeddedImage.
I had a usecase in the past where I grab an bitmap data from the hard disk
and while it
Looks like creating a new model would be the way to go then. I am only
concerned about having to create a new interface/class heirarchy because
only one function's (source, in this case) signature is incompatible.
I saw something about function overloading somewhere. If we get around to
doing
I started with the source being Object but then I realized it might not
make any sense on the JavaScript side so I made it a String. If someone
wanted to load in a SWF, it would make the app unusable on the JavaScript
side, so I would think they would change the beads or there would be a
