Comments on: Flash Catalyst: not just a designer tool - developers workflow techniques

By: Bart

Bart — Tue, 01 Sep 2009 07:31:03 +0000

The code which fc spits out atm is far from organized in contrary what Adobe says. And no one have anny complaints about the file-size increment?

To get integrated with the use of the tool and skinned a plain video player. The result was 10 times bigger in file size then it’s plain-old flash “competitor”. Sure the tool isn’t created to do just these small and simple things though it raises questions on larger projects to…

But as mentioned before it’s still beta! And I keep my hopes up this will be a great tool! Though imho more to the developer then the designer side, nontheless what Adobe promotes.

By: Gilles Guillemin

Gilles Guillemin — Thu, 27 Aug 2009 13:00:02 +0000

Hi,

I’ve just rolled out an alpha version of a tool designed to greatly simplify the exchanges between Flash Catalyst and Flash Builder. It acts as an external synchronization tool between the two of them:
http://www.flexstuff.co.uk/applications/catalystbuildersync/

I thought you might be interested,

Cheers,
Gilles

By: hahaveryfunny

hahaveryfunny — Fri, 07 Aug 2009 14:39:31 +0000

these comments are hilarious

By: Paul

Paul — Thu, 30 Jul 2009 19:05:11 +0000

I keep reminding myself that this is Beta software. I have to believe that Adobe wouldn’t give the program to anyone, as is, for production. I haven’t had the luxury of having a developer who could give any input or feedback into the actual real-life integration vs. Adobe planned workflow integration. What I do love, however, is the potential that this program brings. I also keep reminding myself that this is only a 1.0 launch. Photoshop used to be as well, and look how far it has come since then. Short term, FC (so I can be as cool as you!) is impressive, but not a game changer. Long term, I think this *could* be amazing for the Design/Dev workflow. I am encouraged that Adobe takes user feedback pretty seriously and I hope that they read your post. It’s very insightful for this point in product development.

By: TJ Morris

TJ Morris — Thu, 30 Jul 2009 18:16:44 +0000

As a designer, I work with Elad and have had some hands on experience with FC..(I’ll be cool and call it ‘FC’) From what I see it is basically a glorified Plug In for the other Adobe programs… We’ve found some issues when transitioning a Photoshop or Illustrator.. Little annoying things that the developer had to find in the code and the designer had to figure out what to do to fix it in the graphic file…

I understand by making this a separate plug in for each adobe program would be unfeasible..what with overloading an already bloated set of programs that love to gang-rape the processor especially when more than one is open….

But instead of making a blanket set of tools that KIND OF correspond to PS or Ai (again…shortening names is cool) maybe based on what type of graphics file you import into catalyst… the exact tools from that program will be used. Maybe only major tools… and on top of that have all the interactive component making tools….

Personally I don’t want to have to learn a whole new program that is basically an interactive mock-maker…. By loading up the design with labels and such.. it makes MORE work for the developer who has to clean out your design so he/she can elegantly remake it in code anyway… which from what I remember is kinda what they’ve been doing for years….

By: Flash Scope Component

Flash Scope Component — Wed, 29 Jul 2009 14:46:05 +0000

Flash Catalyst is definitely is one of the greatest Adobe developers ideas right now. What so cool is that now designer don’t think on what flasher can or can’t. We just create it’s awesome design and move it to flasher to work on further.
Thanks for the post!