Support for defining 9-Slices or some kind of resizable, percentage-based components is ESSENTIAL if this is to be used for any real application. An app where everything is fixed size is unmaintainable and quite ridiculous. I can't even make tabbed navigation with catalyst because it can't handle resizing the tabs based on the inner text.

Sure I can fix these issues post-catalyst in Flash Builder, and I can prevent my code being stomped on by keeping everything in external files but it's a drama to worry about the child order or reworking the id's on code after exporting it from Catalyst -> Flash Builder.

This article sums up many of my issues fairly precicely:

I know you've addressed resizing in http://forums.adobe.com/thread/486207 but I'd like to post here to see what kind of support such a feature would get regarding votes. 

Thanks!

It really would be nice if we could click and drag the pages to reorder them. This would help with creating a prototype that has a logical left to right flow.

It would also be nice if we could change the order of our pages/states in the top panel by dragging and dropping!

Allow developers to do round-tripping between FC and Flash Builder. Perhaps some integration with diff/merge tools-

I know this is possible by pulling the Catalyst file into Builder and manually writing code.... but it would be extremely helpful for this option to be available for Catalyst users (code dummies like myself :)

With Fireworks role being described by Adobe as "Rapidly prototype websites and application interfaces with Adobe® Fireworks® CS4 software", and it's user base being so devoted and loyal, I can't understand why it isn't supported directly and fully like Photoshop or Illustrator. It fits the envisioned workflow much better than Illustrator, why not say Photoshop too, and using Fireworks PNG files in Flash Catalyst, with their Pages and States features would be so much more natural and useful.

So please support Fireworks-Flash Catalyst workflow in full.

Thank you for the excellent new tool.

I think that the ability to drag and drop would be very useful for prototyping. I recently had to do this for a prototype and resorted to using flash instead. I was trying to show how one could customize a page by dragging widgets from a side column to the page. 

The way I did it in flash could be transferred to catalyst.

• I applied some basic AS to my MovieClip so it was draggable
• I used a hitTest that caused the destination box to glow when rolled over
•  When the MC was released, my dragged MC turned off while the destination box turned on.

One of the most jarring interface issues in Flash has been the lack of consistent web behaviors for UI elements that are standardized in xhtml. Please support an easy method for FC users to allow optionally activate the scroll bars and scrolling elements for use with the mousewheel, magic mouse, or whatever conventional "mouse-scroller" the user has. As a bonus, it'd be great to easily handle keyboard input as well. Thanks.

I think I know what the answer to this idea is already, but I'm really curious to see what the rest of the FC beta user community thinks:

I think FC users should have the ability to create variables. I also think that basic IF THEN logic should be available. I know that many will say that Interaction Designers don't know/won't use that programming stuff but I don't think that’s true. Axure is a good example of a mature tool that many many interaction designers use. Axure has the ability to set variables and work with conditional logic. Its easy to use and has many uses when the goal is to create a prototype that the user can truly click through.

To me, the need for this arises as soon as you want to create a prototype that has a login element. How do you evaluate login credentials without having some ability to utilize variables and conditional logic-

Variables and conditional logic are the things that set apart the useful and robust wireframing/prototyping tool like Axure a

Many times I want to move from one page state to another after a certain amount of time. For example , I want do simulate doing a search so I want to display a "Searching" indicator for a few seconds and then go to a "Search Results" page state. To do this in Flex you can use a timer; it would be great to have a *basic* timer that transitions between states after a specified time.

I made a quick comp to show what this might look like in Catalyst.