Flash Catalyst Ideas
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.
Lorem
Ipsum
Dolor
Sit
Amet
Lorem Ipsum Dolor Sit Ametv More... |
|
|
|
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! |
|
|
|
hello, i think that it will be a good idea that we will can modify the Id of component on FC, now we can modify only the accessibilityName. it will optimize the work flow. |
|
|
|
D1876 Category: Designer-Develo... Submitted by: steveo de stevelux on 05/19/2010
Status:
New Submission
Tags: access automation designer developer flex illustrator indesign integration limitations photoshop workflow What's missing is a true WYSIWYG for the FLEX framework. Catalyst has the ability to be that but has thus far been laughably equipped to do so. Currently, we need a way for our web designers to redesign an application, assign some CSS styles, MXML ids and assign existing framework event handlers.
Our current workflow: 1. Designer sees framework and would like to aid in the tool's design 2. Pops out an Illustrator design (or Photoshop) 3. Hands over to Flash/FLEX developer to "make it happen" 4. Developer has to author rich/animated buttons in Flash 5. Imports assets into FLEX 6. Starts hammering out UIComponents with CSS to mimic design
Problems: Visual assets will translate defacto into Flash but not into the FLEX Framework. Catalyst's MXML generation is clunky and far from streamlined or modular. I almost wonder why FXG isn't just FLEX. They're both pretty similar in purpose. Either way there's no native way to get MODULAR pieces of a design file into FLEX.
What should happe More... |
|
|
|
Displaying results 1 - 4 of 4 |
Technologies |
Categories |
Tag Cloud |
Community Statistics |
262 | Submissions |
164 | Comments |
1,954 | Votes |
556 | Users |
Top Contributors |
User | Points |
moflebukken | 186 |
JoanaBCunha | 165 |
wadedwalker | 121 |
DanT_ID | 87 |
Breeeee | 67 |
fefe79 | 64 |
2sidesdesign | 64 |
truvak | 64 |
_csfjy | 62 |
olejnik | 58 |
Invite A Friend |
Home | View Ideas | Adobe Labs Home
Copyright © 2010 Adobe Systems Incorporated. All rights reserved.
Your use of the Adobe Labs including the download of software, submission of comments, ideas, feature requests and techniques, and Adobe's rights to use such submitted materials, is governed by the Adobe.com Terms of Use and the Adobe Privacy Policy.
Contact Us: service@brightidea.com |