My Profile

My Info
Ratsnackbar's Profile Photo
Ratsnackbar
My Favorites
none
My Ideas
My Comments
Good Question. I imagine that there are certain underlying complexities inherent in how Catalyst works that would mean editing code live could break the functionality of the UI. So code edits may be locked for a good reason. However I understand that having the ability to completely round trip from Catalyst into Flash Builder is under consideration. If that were the case then those complexities would have to have been worked out already at that point. In that situation I think the ideal solution would be to have the ability to mount your Flash Catalyst project onto a Shared Drive in some location within your network. Then have the ability to mount the same directory in Flash Builder. That way there is no need to export the project in FXP and import it into Flash Builder. Both tools would share the exact same project. Automatic Saving of files on change could be added so that ever edit can be undone regardless of who performed the edit. This would also tie in nicely with a Source Control system. With both tools able to work live with the same project at the same time then a designer can work with the developer in real time. When edits are performed on the code from Flash Builder the code changes dynamically in Flash Catalyst and when modifications are made in FC, FB would auto update. There would have to be some way in the tool/tools to enable this type of Source Sharing between different tools and individuals. Analogous to how Remote Administration software enables the sharing of a desktop to view to multiple individuals at one time where one can control and many can see. You could have an edit code button in Flash Catalyst that when pressed would take you to the Flash Builder utility for the project. In the Flash Builder Visual Editor you could also have a button to take you into the project in Flash Catalyst. By doing it this way you could dynamically work on the project in tandem with your developer and not have to worry about enabling and building a full code editor in Flash Catalyst. The important part here is that both tools regardless of where the project files are actually stored could be worked on live. The actually files could be even hosted on a development server somewhere on a cloud. Anyway the point is that there are many creative ways to allow code editing. Simply enabling the editor in Flash Catalyst might as you say cause issues with the simplicity of FC but using the above methodology (more refined then I suggest) would keep the simplicity intact and add greatly to the overall functionality and usefulness.
Post Idea
Your Statistics
3 submissions
21 votes of support
1 comments
24 points
Community Statistics
262 Submissions
164 Comments
1,954 Votes
556 Users
User Search
Go