You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Harbs <ha...@gmail.com> on 2013/04/15 09:35:56 UTC
CS Extensions
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…
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
On Apr 16, 2013, at 7:26 PM, Alex Harui wrote:
> Thanks for working on this. I have some "process" tasks for you.
>
> 1) I just skimmed the commit email and noticed that the files need Apache
> headers.
Okay. I'll add them.
> 2) I think you mentioned that some of this code was originally written by
> someone else? I think we need an email from him in the mailing list
> archives so we have an official "paper trail". You could forward one from
> him or he can write a new one. We also need to determine what kinds of
> licenses and copyright attributions are required for his work, if any.
I did not get his code yet. I will see him in person in two weeks. It might wait until then. I'll consult with you when that happens...
>
> On 4/16/13 7:33 AM, "Harbs" <ha...@gmail.com> wrote:
>
>> I just pushed an initial skeleton framework of the panel with some placeholder
>> components there to give an idea what the different components look like. Some
>> of the methods I used for styling is a bit hacky, but it worksŠ
>>
>> All the code needed for styling in both a light and dark UI is there. There's
>> also a NativeComboBox which I like to use instead of the normal ComboBox. You
>> can see the difference in behavior if you run the extension.
>>
>> None of the UI layout or functionality implementation is done yet. When I find
>> some time, I'll start with laying something out, unless someone 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:
>>
>>> 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Š
>>>
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: CS Extensions
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Jun 11, 2013 at 3:00 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 6/11/13 2:23 PM, "OmPrakash Muppirala" <bi...@gmail.com> 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 take a look at what the CC subscription costs and see if it
is worth it.
> >
> >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.
> Where's the spec now? If on an Adobe site, then it might come in when
> Michelle gets the rest of the Adobe doc donated.
> >
>
>
I have no idea. I dont see it in the open source website. There is a
lengthy document here: [1] but that does not seem a formal spec document
that can be used programatically.
How does the compiler check an FXG document for correctness?
Thanks,
Om
[1] http://sourceforge.net/adobe/flexsdk/wiki/FXG%202.0%20Specification/
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
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 11:26 AM, Harbs <ha...@gmail.com> 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
>> 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…
>>
>
>
> Harbs,
>
> A couple of days ago, I checked in a project called FXGTools [1]
>
> The tool lets you create discrete FXG files from the AI Symbols library.
> It also optimizes the generated FXG by removing the unnecessary Group
> elements that AI creates.
>
> Can you please take a look at the tool and see what it would take to create
> an AI extension with this?
>
> Thanks,
> Om
>
> [1]
> https://git-wip-us.apache.org/repos/asf?p=flex-utilities.git;a=tree;f=FXGTools;hb=develop
>
>
>
>>
>> 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 <ah...@adobe.com> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On 4/16/13 3:03 PM, "Justin Mclean" <ju...@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
>>>>
>>>>
>>
>>
Re: CS Extensions
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, Jun 12, 2013 at 11:26 AM, Harbs <ha...@gmail.com> 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
> 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…
>
Harbs,
A couple of days ago, I checked in a project called FXGTools [1]
The tool lets you create discrete FXG files from the AI Symbols library.
It also optimizes the generated FXG by removing the unnecessary Group
elements that AI creates.
Can you please take a look at the tool and see what it would take to create
an AI extension with this?
Thanks,
Om
[1]
https://git-wip-us.apache.org/repos/asf?p=flex-utilities.git;a=tree;f=FXGTools;hb=develop
>
> 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 <ah...@adobe.com> wrote:
> >
> >>
> >>
> >>
> >> On 4/16/13 3:03 PM, "Justin Mclean" <ju...@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
> >>
> >>
>
>
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
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 <ah...@adobe.com> wrote:
>
>>
>>
>>
>> On 4/16/13 3:03 PM, "Justin Mclean" <ju...@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
>>
>>
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
On 6/11/13 2:23 PM, "OmPrakash Muppirala" <bi...@gmail.com> 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 was part of the donation, although I dont see a spec document
>(DTD, XSD, etc.) anywhere.
Where's the spec now? If on an Adobe site, then it might come in when
Michelle gets the rest of the Adobe doc donated.
>
Re: CS Extensions
Posted by OmPrakash Muppirala <bi...@gmail.com>.
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 <ah...@adobe.com> wrote:
>
>
>
> On 4/16/13 3:03 PM, "Justin Mclean" <ju...@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
>
>
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
On 4/16/13 3:03 PM, "Justin Mclean" <ju...@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
Re: CS Extensions
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
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" <ha...@gmail.com> 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, Alex Harui wrote:
>
>>
>>
>>
>> On 4/16/13 11:17 AM, "Harbs" <ha...@gmail.com> 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 extensions created by
>>> Adobe
>>> that had dropdowns that extended beyond the bounds of the panels, and
>>> wondered
>>> how to accomplish that. Bob realized that NativeMenu could be used and wrote
>>> an implementation. I have since greatly modified his original
>>> implementation, but the original implementation was his. Do we need his
>>> permission recorded here?
>>>
>> If you have doubts after reading this, then we should contact Apache Legal
>> as only they can give the official ruling.
>>
>> But I think as long as you give attribution in the NOTICE file and include
>> the CC_NC_SA license and the Adobe modifications in the LICENSE file (see
>> [1]), you do not need explicit permission. Apache Legal has ok'd CC_SA
>> licensed works but they did not explicitly ok the NC license (see [2]). I
>> thought the NC part was a deal-breaker [3], but then Adobe overrides that in
>> their modifications [4].
>>
>> Here are some links for your reading pleasure:
>> [1]
>> http://incubator.apache.org/guides/releasemanagement.html#best-practice-lice
>> nse
>> [2] http://www.apache.org/legal/resolved.html
>> [3] http://creativecommons.org/licenses/by-nc-sa/3.0/
>> [4]
>> 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
>>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
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" <ha...@gmail.com> 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 extensions created by Adobe
>> that had dropdowns that extended beyond the bounds of the panels, and wondered
>> how to accomplish that. Bob realized that NativeMenu could be used and wrote
>> an implementation. I have since greatly modified his original
>> implementation, but the original implementation was his. Do we need his
>> permission recorded here?
>>
> If you have doubts after reading this, then we should contact Apache Legal
> as only they can give the official ruling.
>
> But I think as long as you give attribution in the NOTICE file and include
> the CC_NC_SA license and the Adobe modifications in the LICENSE file (see
> [1]), you do not need explicit permission. Apache Legal has ok'd CC_SA
> licensed works but they did not explicitly ok the NC license (see [2]). I
> thought the NC part was a deal-breaker [3], but then Adobe overrides that in
> their modifications [4].
>
> Here are some links for your reading pleasure:
> [1]
> http://incubator.apache.org/guides/releasemanagement.html#best-practice-lice
> nse
> [2] http://www.apache.org/legal/resolved.html
> [3] http://creativecommons.org/licenses/by-nc-sa/3.0/
> [4]
> 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
>
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
On 4/16/13 11:17 AM, "Harbs" <ha...@gmail.com> 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 extensions created by Adobe
> that had dropdowns that extended beyond the bounds of the panels, and wondered
> how to accomplish that. Bob realized that NativeMenu could be used and wrote
> an implementation. I have since greatly modified his original
> implementation, but the original implementation was his. Do we need his
> permission recorded here?
>
If you have doubts after reading this, then we should contact Apache Legal
as only they can give the official ruling.
But I think as long as you give attribution in the NOTICE file and include
the CC_NC_SA license and the Adobe modifications in the LICENSE file (see
[1]), you do not need explicit permission. Apache Legal has ok'd CC_SA
licensed works but they did not explicitly ok the NC license (see [2]). I
thought the NC part was a deal-breaker [3], but then Adobe overrides that in
their modifications [4].
Here are some links for your reading pleasure:
[1]
http://incubator.apache.org/guides/releasemanagement.html#best-practice-lice
nse
[2] http://www.apache.org/legal/resolved.html
[3] http://creativecommons.org/licenses/by-nc-sa/3.0/
[4]
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
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
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 extensions created by Adobe that had dropdowns that extended beyond the bounds of the panels, and wondered how to accomplish that. Bob realized that NativeMenu could be used and wrote an implementation[1]. I have since greatly modified his original implementation, but the original implementation was his. Do we need his permission recorded here?
[1] http://cookbooks.adobe.com/post_ComboBox_that_uses_a_NativeMenu__Air_API_-17533.html
On Apr 16, 2013, at 7:26 PM, Alex Harui wrote:
> Thanks for working on this. I have some "process" tasks for you.
>
> 1) I just skimmed the commit email and noticed that the files need Apache
> headers.
>
> 2) I think you mentioned that some of this code was originally written by
> someone else? I think we need an email from him in the mailing list
> archives so we have an official "paper trail". You could forward one from
> him or he can write a new one. We also need to determine what kinds of
> licenses and copyright attributions are required for his work, if any.
>
>
> On 4/16/13 7:33 AM, "Harbs" <ha...@gmail.com> wrote:
>
>> I just pushed an initial skeleton framework of the panel with some placeholder
>> components there to give an idea what the different components look like. Some
>> of the methods I used for styling is a bit hacky, but it worksŠ
>>
>> All the code needed for styling in both a light and dark UI is there. There's
>> also a NativeComboBox which I like to use instead of the normal ComboBox. You
>> can see the difference in behavior if you run the extension.
>>
>> None of the UI layout or functionality implementation is done yet. When I find
>> some time, I'll start with laying something out, unless someone 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:
>>
>>> 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Š
>>>
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
Thanks for working on this. I have some "process" tasks for you.
1) I just skimmed the commit email and noticed that the files need Apache
headers.
2) I think you mentioned that some of this code was originally written by
someone else? I think we need an email from him in the mailing list
archives so we have an official "paper trail". You could forward one from
him or he can write a new one. We also need to determine what kinds of
licenses and copyright attributions are required for his work, if any.
On 4/16/13 7:33 AM, "Harbs" <ha...@gmail.com> wrote:
> I just pushed an initial skeleton framework of the panel with some placeholder
> components there to give an idea what the different components look like. Some
> of the methods I used for styling is a bit hacky, but it worksŠ
>
> All the code needed for styling in both a light and dark UI is there. There's
> also a NativeComboBox which I like to use instead of the normal ComboBox. You
> can see the difference in behavior if you run the extension.
>
> None of the UI layout or functionality implementation is done yet. When I find
> some time, I'll start with laying something out, unless someone 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:
>
>> 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Š
>>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
I just pushed an initial skeleton framework of the panel with some placeholder components there to give an idea what the different components look like. Some of the methods I used for styling is a bit hacky, but it works…
All the code needed for styling in both a light and dark UI is there. There's also a NativeComboBox which I like to use instead of the normal ComboBox. You can see the difference in behavior if you run the extension.
None of the UI layout or functionality implementation is done yet. When I find some time, I'll start with laying something out, unless someone 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:
> 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…
>
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
Someone has done that already:
http://ajarproductions.com/pages/products/in5/
On Apr 15, 2013, at 10:06 PM, Dave Fisher wrote:
> If this would be indesign to html5. That would be very cool.
>
> Sent from my iPhone
>
> On Apr 15, 2013, at 2:45 PM, Harbs <ha...@gmail.com> wrote:
>
>> I just asked Olav Kvern who's done a bunch of path work for InDesign and Illustrator and he's okay with donating his work to this project. That should help jump-start things very nicely!
>>
>>
>> On Apr 15, 2013, at 9:17 PM, OmPrakash Muppirala wrote:
>>
>>> Drawscript looks good, except that it writes to actionscript/javascript
>>> directly. I dont think that it is a good idea necessarily.
>>> In the case of JS, it is geared towards drawing on the Canvas element.
>>> Problem is that anything drawn on the canvas immediately loses hitTest,
>>> accessibility,etc.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Mon, Apr 15, 2013 at 11:10 AM, Harbs <ha...@gmail.com> wrote:
>>>
>>>> DrawScript looks cool. I would not hold my breath on getting the source
>>>> donated, but if someone wants to try, that would be cool.
>>>>
>>>> On Apr 15, 2013, at 8:37 PM, jude wrote:
>>>>
>>>>> I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
>>
Re: CS Extensions
Posted by Dave Fisher <wa...@apache.org>.
If this would be indesign to html5. That would be very cool.
Sent from my iPhone
On Apr 15, 2013, at 2:45 PM, Harbs <ha...@gmail.com> wrote:
> I just asked Olav Kvern who's done a bunch of path work for InDesign and Illustrator and he's okay with donating his work to this project. That should help jump-start things very nicely!
>
>
> On Apr 15, 2013, at 9:17 PM, OmPrakash Muppirala wrote:
>
>> Drawscript looks good, except that it writes to actionscript/javascript
>> directly. I dont think that it is a good idea necessarily.
>> In the case of JS, it is geared towards drawing on the Canvas element.
>> Problem is that anything drawn on the canvas immediately loses hitTest,
>> accessibility,etc.
>>
>> Thanks,
>> Om
>>
>> On Mon, Apr 15, 2013 at 11:10 AM, Harbs <ha...@gmail.com> wrote:
>>
>>> DrawScript looks cool. I would not hold my breath on getting the source
>>> donated, but if someone wants to try, that would be cool.
>>>
>>> On Apr 15, 2013, at 8:37 PM, jude wrote:
>>>
>>>> I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
>
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
I just asked Olav Kvern who's done a bunch of path work for InDesign and Illustrator and he's okay with donating his work to this project. That should help jump-start things very nicely!
On Apr 15, 2013, at 9:17 PM, OmPrakash Muppirala wrote:
> Drawscript looks good, except that it writes to actionscript/javascript
> directly. I dont think that it is a good idea necessarily.
> In the case of JS, it is geared towards drawing on the Canvas element.
> Problem is that anything drawn on the canvas immediately loses hitTest,
> accessibility,etc.
>
> Thanks,
> Om
>
> On Mon, Apr 15, 2013 at 11:10 AM, Harbs <ha...@gmail.com> wrote:
>
>> DrawScript looks cool. I would not hold my breath on getting the source
>> donated, but if someone wants to try, that would be cool.
>>
>> On Apr 15, 2013, at 8:37 PM, jude wrote:
>>
>>> I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
>>>>
>>>>
>>
>>
Re: CS Extensions
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Drawscript looks good, except that it writes to actionscript/javascript
directly. I dont think that it is a good idea necessarily.
In the case of JS, it is geared towards drawing on the Canvas element.
Problem is that anything drawn on the canvas immediately loses hitTest,
accessibility,etc.
Thanks,
Om
On Mon, Apr 15, 2013 at 11:10 AM, Harbs <ha...@gmail.com> wrote:
> DrawScript looks cool. I would not hold my breath on getting the source
> donated, but if someone wants to try, that would be cool.
>
> On Apr 15, 2013, at 8:37 PM, jude wrote:
>
> > I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
> >>
> >>
>
>
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
DrawScript looks cool. I would not hold my breath on getting the source donated, but if someone wants to try, that would be cool.
On Apr 15, 2013, at 8:37 PM, jude wrote:
> I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
>>
>>
Re: CS Extensions
Posted by jude <fl...@gmail.com>.
I'm all for this! I think we should at least 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 <ha...@gmail.com> 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…
>
>
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
One or all of these are required (assuming we want compatibility for CS5 and forward. If it's CS6 and forward they will be slightly different)):
apeddelta.swc
CSXSLibrary-2.0-sdk-3.4-public.swc
csaw_illustrator.swc
csaw_indesign.swc
csaw_photoshop.swc
MXThemeSync.swc
The csaw libs are only necessary if we do the application scripting in ActionScript. I tend to do that very often in ExtendScript (Javascript). So, they might not be strictly necessary.
I usually use one or more of the following, but I don't see off the bat why we'll necessarily need them:
as3commons.swc
as3crypto.swc
as3corelib.swc
On Apr 15, 2013, at 6:48 PM, Alex Harui wrote:
>
>
>
> On 4/15/13 1:19 AM, "Harbs" <ha...@gmail.com> 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Š
>>>>
>>>>
>>> We can always have a build script that downloads the required external
>>> dependencies. As long as they are of compatible licenses and we dont check
>>> them into our repos, we should be fine. After all, the Flex SDK depends on
>>> Flash Player, AIR, Batik, etc. The build script just downloads them for
>>> the user (after a license confirmation)
>>>
>>> Please let me know how I can help.
> There is a difference in the treatment of the Flash Player and AIR SDKs,
> which do not have Apache compatible licenses and are considered build tools
> since the SWCs do not have code that goes in the output SWF, and the
> OSMF.swc which does have a compatible license and whose code might go in the
> SWF. And yet another treatment for the embedded font library, which does
> not have a compatible license and therefore must only be used for optional
> features.
>
> Which SWCs are you going to need and/or optionally need and where can we get
> licensing information on them?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
On 4/15/13 1:19 AM, "Harbs" <ha...@gmail.com> 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Š
>>>
>>>
>> We can always have a build script that downloads the required external
>> dependencies. As long as they are of compatible licenses and we dont check
>> them into our repos, we should be fine. After all, the Flex SDK depends on
>> Flash Player, AIR, Batik, etc. The build script just downloads them for
>> the user (after a license confirmation)
>>
>> Please let me know how I can help.
There is a difference in the treatment of the Flash Player and AIR SDKs,
which do not have Apache compatible licenses and are considered build tools
since the SWCs do not have code that goes in the output SWF, and the
OSMF.swc which does have a compatible license and whose code might go in the
SWF. And yet another treatment for the embedded font library, which does
not have a compatible license and therefore must only be used for optional
features.
Which SWCs are you going to need and/or optionally need and where can we get
licensing information on them?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: CS Extensions
Posted by Harbs <ha...@gmail.com>.
I'm a bit crazy for trying to start this right now. I'm off to a conference in less than two weeks, and time is not exactly a commodity in large supply right now… ;-)
It will likely remain largely a skeleton for a few weeks, but at least I can get it started. I figure the support will come in stages. Where do you think I should start? I figure I'll start with Rect and add attributes to that until it's more-or-less complete. It can grow organically from there. Makes sense?
I was thinking of starting it on a whiteboard, but I guess the utilities repro makes sense. If there's no objections, I'll start it there.
Harbs
On Apr 15, 2013, at 10:42 AM, OmPrakash Muppirala wrote:
> Exciting stuff! I would love to help you on this one, time permitting.
>
> On Mon, Apr 15, 2013 at 12:35 AM, Harbs <ha...@gmail.com> 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?
>>
>
> 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…
>>
>>
> We can always have a build script that downloads the required external
> dependencies. As long as they are of compatible licenses and we dont check
> them into our repos, we should be fine. After all, the Flex SDK depends on
> Flash Player, AIR, Batik, etc. The build script just downloads them for
> the user (after a license confirmation)
>
> Please let me know how I can help.
>
> Thanks,
> Om
Re: CS Extensions
Posted by Alex Harui <ah...@adobe.com>.
FWIW, Adobe made the CS extension for PS available here:
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p2_mac_093010.
zxp
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p2_win32_09301
0.zxp
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p2_win64_09301
0.zxp
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p3_mac_050311.
zxp
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p3_win32_05031
1.zxp
http://download.macromedia.com/pub/photoshop/photoshopcs5_fxg_p3_win64_05031
1.zxp
I have no idea what is in these downloads or what is the right version for
you, so good luck.
-Alex
On 4/15/13 12:42 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
> Exciting stuff! I would love to help you on this one, time permitting.
>
> On Mon, Apr 15, 2013 at 12:35 AM, Harbs <ha...@gmail.com> 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?
>>
>
> 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Š
>>
>>
> We can always have a build script that downloads the required external
> dependencies. As long as they are of compatible licenses and we dont check
> them into our repos, we should be fine. After all, the Flex SDK depends on
> Flash Player, AIR, Batik, etc. The build script just downloads them for
> the user (after a license confirmation)
>
> Please let me know how I can help.
>
> Thanks,
> Om
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: CS Extensions
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Exciting stuff! I would love to help you on this one, time permitting.
On Mon, Apr 15, 2013 at 12:35 AM, Harbs <ha...@gmail.com> 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?
>
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…
>
>
We can always have a build script that downloads the required external
dependencies. As long as they are of compatible licenses and we dont check
them into our repos, we should be fine. After all, the Flex SDK depends on
Flash Player, AIR, Batik, etc. The build script just downloads them for
the user (after a license confirmation)
Please let me know how I can help.
Thanks,
Om