On 1/25/13 11:00 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:

> 2) Actually, I have the AS implementation completely finished... it's
> the Flex SDK (hence the 'vanilla' in the name). On the browser side
> I'll have to create a JS framework that has the same public API as the
> Flex SDK, but I never said that behind that API would be a translation
> of any unused code from the Flex SDK (would be silly, wouldn't it?),
> nor will it necessarily use the same intertwined dependencies.
OK, I'll believe you, but one of the problems in the current Flex SDK is
interwined dependencies caused by the use of complex classes in the API
surface itself.  I'm not clear how you can fix that without changing the API
surface.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Reply via email to