Hi Om,

I've been drowning (in work) lately… :-(

I'll try to get onto it.

What does the code that you need to import look like? I'll be happy to help 
with that.

A could also ask the the product manager about getting an Extension Builder 
license.

Extension Builder 3 should get more interesting. That has HTML5 support. I'm 
hoping we'll be able to integrate the Apache Flex HTML stuff with that…

On Jun 12, 2013, at 12:23 AM, OmPrakash Muppirala wrote:

> Harbs,
> 
> Any update on this?
> 
> In terms of functionality, I would really like this:
> 
> In Illustrator, there is currently no straightforward way (AFAIK) to
> convert the Symbols library into individual .fxg files.  What I have been
> doing is to convert the whole document into .fxg, parse the Library node
> and create a new file for each symbol encountered.  There is a similar tool
> in the flex-external project although I have not been able to figure out
> how that worked.
> 
> I have an AIR app that does this today, I would like to port it to your CS
> extension framework project that you checked into flex-utilities.  Can you
> please explain how I can start with that?  Also, I dont have an Extension
> Builder license, is it possible to do this work without Extension Builder?
> 
> Alex, any chance you could snag us an open source license for Adobe
> Extension Builder?
> 
> Also, was the spec for FXG donated?  I see in the Adobe Flex White paper
> that FXG was part of the donation, although I dont see a spec document
> (DTD, XSD, etc.) anywhere.
> 
> Thanks,
> Om
> 
> On Tue, Apr 16, 2013 at 3:31 PM, Alex Harui <aha...@adobe.com> wrote:
> 
>> 
>> 
>> 
>> On 4/16/13 3:03 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>> 
>>> Hi,
>>> 
>>>> Sounds like gobbledygook to me. Should I just ask Bob to give his okay
>> to be
>>>> sure? I think the code he wrote was on his own timeŠ
>>> 
>>> Which probably still mean Adobe owns it if he's a full time employee at
>> Adobe
>>> - so we may need to get permission from them.
>> Good point regarding copyright ownership.  It is probably copyright Adobe.
>> Regarding permission, this link [1] implies that it isn't necessary, and
>> even if you think it is, the "author" gives permission.
>> 
>> [1]
>> 
>> http://www.adobe.com/communities/guidelines/ccplus/commercialcode_plus_permi
>> ssion.html
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
>> 

Reply via email to