Hi Om,
I noticed the check-in.
I'll try to take a look at it.
I'm hoping that I'll have time now that (most of) my kids are going back to
school. Things have not exactly been working out as I planned… :-(
Harbs
On Aug 6, 2013, at 1:57 AM, OmPrakash Muppirala wrote:
> On Wed, Jun 12, 2013 at
On Wed, Jun 12, 2013 at 11:26 AM, Harbs wrote:
> 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
>
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
On Tue, Jun 11, 2013 at 3:00 PM, Alex Harui wrote:
>
>
> On 6/11/13 2:23 PM, "OmPrakash Muppirala" wrote:
> >
> >Alex, any chance you could snag us an open source license for Adobe
> >Extension Builder?
> I'll ask, but I think Adobe wants you to sign up for Creative Cloud.
>
>
Thanks! I will ta
On 6/11/13 2:23 PM, "OmPrakash Muppirala" wrote:
>
>Alex, any chance you could snag us an open source license for Adobe
>Extension Builder?
I'll ask, but I think Adobe wants you to sign up for Creative Cloud.
>
>Also, was the spec for FXG donated? I see in the Adobe Flex White paper
>that FXG
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
On 4/16/13 3:03 PM, "Justin Mclean" 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 g
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.
Justin
If that's easy to do, it probably wouldn't hurt. Otherwise we should get
official answers.
On 4/16/13 2:04 PM, "Harbs" wrote:
> 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Š
>
> On Apr 16, 2013, at 11:37 PM,
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…
On Apr 16, 2013, at 11:37 PM, Alex Harui wrote:
>
>
>
> On 4/16/13 11:17 AM, "Harbs" wrote:
>
>> There's one other issue with my code:
>>
>> All the code is min
On 4/16/13 11:17 AM, "Harbs" wrote:
> There's one other issue with my code:
>
> All the code is mine with the partial exception of NativeComboBox.
>
> NativeComboBox was the result of a discussion between Bob Stucky (a friend and
> Adobe employee) and me. I observed that there were extension
eone else gets to
>> it first.
>>
>> In terms of a UI, I'm thinking of populating a TextArea with the FXG XML that
>> can be copied and pasted elsewhere or a direct export to file.
>>
>> Harbs
>>
>> On Apr 15, 2013, at 10:35 AM, Harbs wrote:
>&
> Harbs
>>
>> On Apr 15, 2013, at 10:35 AM, Harbs wrote:
>>
>>> I'd like to start that project to export FXG from creative suite apps.
>>>
>>> Some questions:
>>> 1) Should I start this on a personal github account, or have we settled
>> I'd like to start that project to export FXG from creative suite apps.
>>
>> Some questions:
>> 1) Should I start this on a personal github account, or have we settled on
>> something else?
>> 2) CS Extensions have dependencies on a number of Adobe swcs. How do
e suite apps.
>
> Some questions:
> 1) Should I start this on a personal github account, or have we settled on
> something else?
> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
> handle the project vis a vis Apache's policies and binaries? I don't think
> those dependencies can be included…
>
t FXG export extensions or have they been donated already?
>>>> Also,
>>>>> check out DrawScript <http://drawscri.pt>.
>>>>>
>>>>>
>>>>> On Mon, Apr 15, 2013 at 2:35 AM, Harbs wrote:
>>>>>
>>>>
attempt to get the source to
>>>> the current FXG export extensions or have they been donated already?
>>> Also,
>>>> check out DrawScript <http://drawscri.pt>.
>>>>
>>>>
>>>> On Mon, Apr 15, 2013 at 2:35 AM, Harbs wrote:
>>>
013 at 2:35 AM, Harbs wrote:
>>>
>>>> I'd like to start that project to export FXG from creative suite apps.
>>>>
>>>> Some questions:
>>>> 1) Should I start this on a personal github account, or have we settled
>> on
>>>> something else?
>>>> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
>>>> handle the project vis a vis Apache's policies and binaries? I don't
>> think
>>>> those dependencies can be included…
>>>>
>>>>
>>
>>
7;d like to start that project to export FXG from creative suite apps.
> >>
> >> Some questions:
> >> 1) Should I start this on a personal github account, or have we settled
> on
> >> something else?
> >> 2) CS Extensions have dependencies on a number o
Should I start this on a personal github account, or have we settled on
>> something else?
>> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
>> handle the project vis a vis Apache's policies and binaries? I don't think
>> those dependencies can be included…
>>
>>
to export FXG from creative suite apps.
>
> Some questions:
> 1) Should I start this on a personal github account, or have we settled on
> something else?
> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
> handle the project vis a vis Apache's po
c
as3crypto.swc
as3corelib.swc
On Apr 15, 2013, at 6:48 PM, Alex Harui wrote:
>
>
>
> On 4/15/13 1:19 AM, "Harbs" wrote:
>
>
>>>
>>>> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
>>>> handle the project vis
On 4/15/13 1:19 AM, "Harbs" wrote:
>>
>>> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
>>> handle the project vis a vis Apache's policies and binaries? I don't think
>>> those dependencies can be included
t that project to export FXG from creative suite apps.
>>
>> Some questions:
>> 1) Should I start this on a personal github account, or have we settled on
>> something else?
>>
>
> What do you think of the flex-utilities git repo?
>
>
>> 2) CS Extensions
t that project to export FXG from creative suite apps.
>>
>> Some questions:
>> 1) Should I start this on a personal github account, or have we settled on
>> something else?
>>
>
> What do you think of the flex-utilities git repo?
>
>
>> 2) CS Exten
ave we settled on
> something else?
>
What do you think of the flex-utilities git repo?
> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we
> handle the project vis a vis Apache's policies and binaries? I don't think
> those dependencies can be included…
I'd like to start that project to export FXG from creative suite apps.
Some questions:
1) Should I start this on a personal github account, or have we settled on
something else?
2) CS Extensions have dependencies on a number of Adobe swcs. How do we handle
the project vis a vis Apa
27 matches
Mail list logo