Make use of the extension framework and extension manager, so that the community can solve some of the issues that have been noted.

The recent changes for import/export functionality between Catalyst and Builder is a step in the right direction, but what I would like to see is allowing both to work from the same source without the need to import/export. The change would be to allow Catalyst to open (and save back) either an FXP file or a Builder project folder. This way, designers and developers could work from the same source and have a better workflow when integreting with source file repositories.


Second, I'd also like to see better use of the Catalyst designer xml namespace in the source code generation. For instance, allowing the designer and developer to utilize different dataProviders in a list for design mode and actual developer implementation. This would allow the designer to continue to work with and utilize dummy data to attach renderers to while the developer wires the list to data services. 


Example:

Lorem

Ipsum

Dolor

Sit

Ametv

Why isn't there a data grid that can capture any type of element (text, video, pictures, etc.) included?

It's also time to start including the live and streaming video and recorded audio components, features, and video in these products.

More needs to be added in regards to components.

Finally, I would like to see and learn from my fellow developer.  Maybe a repository of screencasting accessible from a single page.

We need to be able to construct our own extensible and reusable components with ease.  That is not possible now.  I should be able to add and define my own property elements , click states, and interactions either by right clicking and selecting without limit (and/or a little bit of coding).  The current Custom Component is not that usable.

The code view offers little use.  Do we have to depend on moving back and forth to Flash Builder all the time?

I should be able to add links and mailto withinside of text instead of creating a button which is more work on my part.  Besides, creating buttons instead of hyperlinks can get messy to create.

In my opinion, for as long as garbage collection and memory usage continue to be an issue Adobe shouldn't be wasting time on fluff like this. Focus on fixing the issues with the actual flash player.

The ability to import a Flash Professional .fla file format into Catalyst would be a great benefit. Especially since there was an official workflow between Flash Pro and Flex 3 for creating graphical, stateful skins for flex (ie File...New...Flex Skins). It seems strange that in the new workflow, Flash is not treated as a first class citizen such as Illustrator or Photoshop. For large libraries of Flash built skins, the process of converting these to Flex 4 skins is quite painful as the current builds of Catalyst merely provide Importing of FXG. When a Flash-created Flex skin symbol is exported as .fxg from Flash, and imported into Catalyst, only the first frame/state is available.

Having the ability to script the Adobe Flash Catalyst product in the same way that one can with Flash's JSFL, Fireworks, Illustrator, etc would be a great benefit. Specifically, but not limited to, the ability to import .fxg, convert to component, save project.

It would be nice to have components that look like they are sketched in pencil (like Balsamiq.com). Sometimes it is nice to have lower fidelity (or loose) looking prototypes when testing the behaviour of an interface. You don't want your users getting hung up on the aesthetics of the inteface when really all you want to do is make sure it behaves and functions properly. I find that the wireframe mode in Catalyst is even too polished for some testing. Knock it down a notch. Creating a fun sketchy looking UI could really help. You could have high fidelity, medium fidelity (wireframe), and low fidelity (loose hand drawen) components.

Well the title says it all. This would make the workflow go so much faster! Having to recreate a set of transitions for each navigation button on each page takes forever. For example: A very small website could have 5 buttons on 5 pages. This means having to recreate the transition 25 times! For a SMALL site... Sorry guys, but "Smooth Transition" is worthless for this!

It would be fantastic if designers/developers had the option to publish to Javascript. I know, I know, there's a mini-war going on between Adobe and Apple over SWF and FLV viewing on mobile devices, but publishing to Javascript, especially if it taps into the jQuery library would make this product BEYOND incredible.