Comments on: Adobe MAX. Blog #5. Day 2. http://flexblog.faratasystems.com/2008/11/20/adobe-max-blog-5-day-2 A blog about our experience with Adobe Flex Wed, 10 Mar 2010 17:11:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: James Polanco http://flexblog.faratasystems.com/2008/11/20/adobe-max-blog-5-day-2/comment-page-1#comment-37205 James Polanco Thu, 20 Nov 2008 17:01:48 +0000 http://flexblog.faratasystems.com/?p=377#comment-37205 Yakov, You are really close with the Catalyst workflow, but Catalyst itself saves an FXP file, not FXG. FXP is a zip file that contains a Flex project that can then be shared between Flex Build and Catalyst. FXG is the XML based markup language that represents Flash Player content (rects, circles, blurs, etc). AI, PS, and FW can export their content as FXG which either Catalyst or Flex Builder can then use directly. In most cases, FXG would be handed directly from one of the supported design tools directly to the Flex developer. I believe the naming follows this pattern: FXG = FleX Graphics, FXP = FleX Project. Its really confusing, I know that during our sessions we stumbled on FXG/FXP word at least once when explaining the proposed workflow process. BTW - I really enjoyed your comments on the Architecture panel. Its great to hear a fellow architect who doesn't like large framework / micro-architecture use in Flex. That is exactly how I feel and it was validating to hear others say the exact same thing I tell my clients and/or fellow developers. Yakov,
You are really close with the Catalyst workflow, but Catalyst itself saves an FXP file, not FXG. FXP is a zip file that contains a Flex project that can then be shared between Flex Build and Catalyst. FXG is the XML based markup language that represents Flash Player content (rects, circles, blurs, etc). AI, PS, and FW can export their content as FXG which either Catalyst or Flex Builder can then use directly. In most cases, FXG would be handed directly from one of the supported design tools directly to the Flex developer. I believe the naming follows this pattern: FXG = FleX Graphics, FXP = FleX Project. Its really confusing, I know that during our sessions we stumbled on FXG/FXP word at least once when explaining the proposed workflow process.

BTW – I really enjoyed your comments on the Architecture panel. Its great to hear a fellow architect who doesn’t like large framework / micro-architecture use in Flex. That is exactly how I feel and it was validating to hear others say the exact same thing I tell my clients and/or fellow developers.

]]>