My Books

  • Follow me on Twitter
My Photo

Subscribe my blog

  • Get this widget from Widgetbox
  • Add to Google
  • RSS FEEDS
  • Enter your Email here to subscribe :



    Powered by FeedBlitz

Blog Widget by LinkWithin

« Securing and optimizing SQLite statements in AIR 1.5 using named or unnamed parameters | Main | The Essential Guide to Flash CS4 AIR Development book has a front cover and a foreword by an Adobe Evangelist »

Comments

Ivo

Looking at the Catalyst output reminds me of Dreamweaver or FrontPage HTML. It looks good but its fat very verbose code. I think client developers are safe, Catalyst will get the look &feel but the performance and component creation will be handled by devs.

cisnky

Flex client developers are going nowhere. Microsoft Expression said something similar and my experience has not been the greatest. Yes the tool will save us developers from having to take a psd or illustrator file and cut it up into the relevant graphic objects, but it won't stop us from ripping out the and tidying up code that is outputted during the whole process.

Rob McKeown

I don't think the goal of Catalyst is to put client developers out of business. The intent, to me, seems to be to allow for designers to take their vision further, allowing them to communicate to developers what they are actually asking for. Any designer who has handed both static screenshots and a working prototype to a developer will agree that the working prototype adds much more value. Catalyst should make the creation of that prototype something most designers can do.

jlgaustin

I work at a company that does enterprise application development and I doubt very seriously that the caliber of components and types of applications we develop that Catalyst will be able to handle. I see this as being a great too for prototyping idea's, trying out effects and transitions quicker. It is being presented as a design tool not a development tool.

Il Douche

Are you kidding me? You're experience in developing flex apps must be limited to mxml and zero actionscript or use of frameworks. Or maybe you are developing REALLY simple apps. You should want to investigate and learn more about the things you are trying to blog about.

Alan Klement

I've been informed on Thermo/Catalyst for quite some time and unless the Catalyst team adds more features and capabilities, this application will be a great dissapointment to most people. So far, Ivo and jlgaustin are correct - it is severely lacking any 'real' power, and is little more than a 'design view' similar to Dreamweaver.
Great - so this app writes code , that will have to be rewritten anyway by a developer, and it allows a designer to assign skins to components, but they can do that faster and easier already.

What possible need does this fill that there isn't already a successful solution for? Flash animating and designing is already a simplified After Effects and Illustrator, now Catalyst is going to be a simplified Flash IDE.

Yohan Araújo

I really don't think that Catalyst will be the killer of RIA applications.The goal of it is accelerate and simplify the development with Flex and Air.What I think that could happen is Flex and Catalyst become one application.

Maikel Sibbald

Oh come on, marco.....You want me to look for a job now :P
What about custom components, making use of libraries like away3d
We, flex developers, can still beat this thing!!!

But yeah, it makes the transition between desinger and developers much easier... I love it!

FC 4 ever ;)

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment