Adobe tools are not under the control of Apache Flex. If those tools stop importing and exporting FXG, Apache Flex can't really do anything about it. Now some of the file formats of the popular tools are documented so anyone can write a conversion tool for those and choose any namespace to manage information not directly tied to the rendering.
On 3/18/13 1:40 PM, "Sebastian Mohr" <flex.masul...@gmail.com> wrote: > Sorry Alex, > > I was a little mixing the topics here. My basic concern is about loosing > the FXG extension support in the Adobe design tools [1] [2], and, the > interconnection to Apache Flex that is dependent on FXG for now. Knowing > the internals of the other namespaces of FXG would be beneficial in case > Adobe would stop FXG support in their design tools like Photoshop CS6 > (and later), Illustrator CS6 (and later) and Fireworks CS6 (and later), > because > then, we would have to write our own FXG extensions for Apache Flex > designers. > > Sorry, you git and compiler guys on this list, > bothering you with design related stuff here! > > > [1] FXG 2.0 donation progress concerns and Adobe design tool support > http://markmail.org/search/?q=+list%3Aorg.apache.incubator.flex-dev+fxg#query: > %20list%3Aorg.apache.incubator.flex-dev%20fxg+page:1+mid:v6w4z3cqswe7ghqn+stat > e:results > > [2] FXG Extension for Photoshop CS5 > http://markmail.org/search/?q=+list%3Aorg.apache.incubator.flex-dev+fxg#query: > %20list%3Aorg.apache.incubator.flex-dev%20fxg+page:1+mid:4kamrcjzm4jbhgh7+stat > e:results > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
