Comments on: Why Adobe chose FXG over SVG http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/ code = joy Thu, 08 Jan 2009 10:58:51 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Adobe Replaces SVG with FXG | Enetlive.net- Rich Internet Applications Blog http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14322 Adobe Replaces SVG with FXG | Enetlive.net- Rich Internet Applications Blog Fri, 10 Oct 2008 02:47:05 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14322 [...] Blog Posts: Mike Chamber Blog Post - Why Adobe Chose FXG Over SVG [...] [...] Blog Posts: Mike Chamber Blog Post - Why Adobe Chose FXG Over SVG [...]

]]> By: Flex Monkey Patches » Blog Archive » Rubbernecker’s Review - Week 15 http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14271 Flex Monkey Patches » Blog Archive » Rubbernecker’s Review - Week 15 Tue, 07 Oct 2008 14:31:58 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14271 [...] Why Adobe chose FXG over SVG (from Mike Chambers) [...] [...] Why Adobe chose FXG over SVG (from Mike Chambers) [...]

]]> By: todd http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14232 todd Wed, 01 Oct 2008 13:42:06 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14232 I'm not too worried about Adobe not supporting SVG. I'm sure there will be tools or some third-party API that might help convert such to FXG. People have been doing this for Silverlight. I guess I'm more interested on what SVG can do that FXG cannot. I’m not too worried about Adobe not supporting SVG. I’m sure there will be tools or some third-party API that might help convert such to FXG. People have been doing this for Silverlight. I guess I’m more interested on what SVG can do that FXG cannot.

]]> By: Frank Spangenberg http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14231 Frank Spangenberg Wed, 01 Oct 2008 12:06:44 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14231 I totally agree with Dan Martin, it's like every Adobe developer group is creating their own file formats for interchange between application A and B, B and A, C and A, C and B etc. At the end we'll have 10 apps and 100 file formats. Somebody totally misunderstood the approach of STANDARDS! And if FXG is so close to SVG, why don't you just improve SVG? Because you're loosing the USP? “You” are looking at SVG like if it's a fixed non-changeable standard... And what's the difference between a “non-standard implementation of SVG” and a not standardized FXG? I totally agree with Dan Martin, it’s like every Adobe developer group is creating their own file formats for interchange between application A and B, B and A, C and A, C and B etc. At the end we’ll have 10 apps and 100 file formats. Somebody totally misunderstood the approach of STANDARDS!

And if FXG is so close to SVG, why don’t you just improve SVG? Because you’re loosing the USP? “You” are looking at SVG like if it’s a fixed non-changeable standard…

And what’s the difference between a “non-standard implementation of SVG” and a not standardized FXG?

]]> By: Tek http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14229 Tek Wed, 01 Oct 2008 10:35:13 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14229 It's too bad that we could not use SVG for Flash graphics and searchable content, but I find hundred times worst not to have a standard way to use FXG (or SVG) from the HTML page to use it at runtime in Flash. We really need to execute FXG from the HTML page, it would allow to create full readable content for "Search Engines" and text readers. And it would help to silence a little those who tell you all the day long that Javascript is much easy to integrate and deploy than Flash for UI Design. It could be our better argument against nowadays Javascript conquerors (the best would be to have Actionscript evaluation ... but we couldn't for the moment). I've started to develop something that read custom XML block from HTML with ExternalInterface but it is not HTML valid if I remember. The only standard way to read FXG from HTML is to write XML content inside the OBJECT tag. But its content couldn't be read from Javascript nor ExternalInterface so. Could it be possible to change the Flash Player to initialize it with FXG tags coming from the tag ? Would it be in any Adobe plan to parse FXG at runtime and to do so ? It’s too bad that we could not use SVG for Flash graphics and searchable content, but I find hundred times worst not to have a standard way to use FXG (or SVG) from the HTML page to use it at runtime in Flash.

We really need to execute FXG from the HTML page, it would allow to create full readable content for “Search Engines” and text readers. And it would help to silence a little those who tell you all the day long that Javascript is much easy to integrate and deploy than Flash for UI Design. It could be our better argument against nowadays Javascript conquerors (the best would be to have Actionscript evaluation … but we couldn’t for the moment).

I’ve started to develop something that read custom XML block from HTML with ExternalInterface but it is not HTML valid if I remember. The only standard way to read FXG from HTML is to write XML content inside the OBJECT tag. But its content couldn’t be read from Javascript nor ExternalInterface so.

Could it be possible to change the Flash Player to initialize it with FXG tags coming from the tag ? Would it be in any Adobe plan to parse FXG at runtime and to do so ?

]]> By: Dan Martin http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14227 Dan Martin Wed, 01 Oct 2008 07:11:32 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14227 I work with Adobe products for a living, and am probably the prime audience for Thermo -- I spend about 50% of my time developing prototypes in Flex. So, I find this discussion interesting, but I'm not as willing to give it a free pass as the previous commenters. I guess I have to ask, since Adobe was involved in the creation of SVG and participates in its maintenance, why cant' these limitation be addressed there? Secondly, the SVG spec does have extensibility support with a mind towards including viable extensions in future specs: http://wiki.svg.org/SVG_Extensions I find Mark Ander's explanation to be fairly unconvincing. It kind of reads like someone who wants to make a new spec. For instance, he says "Flex doesn't provide a DOM of the MXML document so there's no way to look up an object with a specific ID". Maybe I'm crazy, but I'm pretty sure there are multiple ways to lookup an object by ID in Flex(MyMXML.myPropery, MyMXML["myProperty"]), so I guess I just don't get it. On most of his other points, I believe SVG extensions could likely address the issue. I find the whole topic of Adobe and open formats rather frustrating. I work with Adobe products for a living, and am probably the prime audience for Thermo — I spend about 50% of my time developing prototypes in Flex. So, I find this discussion interesting, but I’m not as willing to give it a free pass as the previous commenters.

I guess I have to ask, since Adobe was involved in the creation of SVG and participates in its maintenance, why cant’ these limitation be addressed there?

Secondly, the SVG spec does have extensibility support with a mind towards including viable extensions in future specs: http://wiki.svg.org/SVG_Extensions

I find Mark Ander’s explanation to be fairly unconvincing. It kind of reads like someone who wants to make a new spec. For instance, he says “Flex doesn’t provide a DOM of the MXML document so there’s no way to look up an object with a specific ID”. Maybe I’m crazy, but I’m pretty sure there are multiple ways to lookup an object by ID in Flex(MyMXML.myPropery, MyMXML["myProperty"]), so I guess I just don’t get it. On most of his other points, I believe SVG extensions could likely address the issue.

I find the whole topic of Adobe and open formats rather frustrating.

]]> By: isriya http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14225 isriya Wed, 01 Oct 2008 06:36:01 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14225 Mike, any idea about next speaking tour in Thailand/Southeast Asia? Mike,

any idea about next speaking tour in Thailand/Southeast Asia?

]]> By: Dusty http://www.mikechambers.com/blog/2008/09/30/why-adobe-chose-fxg-over-svg/comment-page-1/#comment-14223 Dusty Wed, 01 Oct 2008 05:28:10 +0000 http://www.mikechambers.com/blog/?p=1550#comment-14223 As long as it's easy to convert from one to the other, I think it's all good. As long as it’s easy to convert from one to the other, I think it’s all good.

]]>