On 1/25/13 10:33 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> Hans,
>
>> But if I understand it correctly, wouldn't it mean in Erik's model that when
>> I create my own custom datagrid component for instance, I would also have to
>> write a JS version for this? (For me personally this is what I would want to
>> avoid -- writing JS myself :) )
>
> No, it wouldn't mean that necessarily . Since we're implementing all
> AS language features in JS, so you should be able to subclass the AS
> component. If you're talking brand new component though, sure, you'd
> have to write both an AS and a JS component. Which actually gives me
> an idea... [walks to his main computer, lost in thought]
>
My answer was going to be: If you have existing code in your subclass that
uses the Flash APIs, then you will either need to write the JS equivalent,
or maybe there will be enough emulation of the FlashPlayer to get it to
work.
In the framework I'm working on, you have the same problem, but I am
starting from a different point: I am saying don't use the Flash APIs in
your subclasses in the first place. I'm hoping to create a framework that
leverages lots of little pieces composited together, and customization will
be more about adding or replacing new little pieces. Hopefully, even skins
will be compositions of bitmaps and other components and less vector
graphics (at least in the early versions), and thus your customizations are
more likely to cross-compile cleanly and not require flash player emulation.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
