Technologies
Tag Cloud
9slice   access   acrobat   actionscript   alignment   and   builder   buttons   catalyst   cmposition   code   color   compatibility   component   components   copying   custom   custom_components   customize   data   design   drag   drop   embed   export   extra   field   fireworks   flash   flashcatalyst   flex   form   gallery   html   id   illustrator   image   import   indesign   integration   interactions   javascript   jquery   layers   library   libraryexport   links   name   pdf   photoshop   photoslider   ppt   preloader   properties   psd   publishing   resize   resolution   reuse   saturation   scroll   share   skin   skinning   state   states   store   swap   swf   template   text   timeline   tools   touch   txt   usability   view   wireframe   workflow   workspace  
Community Statistics
262 Submissions
164 Comments
1,954 Votes
556 Users
Invite A Friend
This Idea is hidden. Change Visibility
Full FLEX project introspection for CSS, Classes and Functions
(D1876)
7
Vote Score
Submitted:
05/19/2010
Status: 
New Submission

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 happen is something like this since the web designer is very Flash savvy but not at all FLEX savvy:

1. Designer sees framework and would like to aid in the tool's design

2. Pops out an Illustrator design (or Photoshop) - heck I'll even say InDesign because you could implement MXML visual objects and FLEX CSS in there probably the easiest with things like group components.

3. Designer migrates assets into Catalyst visually

4. Catalyst can introspect the FLEX project at hand and glean all public methods and CSS classes

5. Designer hooks up the appropriate id and styleName properties for MXML components and even assigns event handlers!

6. Designer then puts compiled SWF into automated system (I could even go for raw MXML for version control) and any CSS updates they deemed necessary.

7. Automated system pulls in SWF (or generates it from MXML) and CSS file

8. Custom framework pulls in the mere 3-5% of visual code needed to reskin it and integrates it fully with all its business logic.

 

Aside from the developer matching MXML/CSS up to the design - our only option we have is for designers to start authoring visual elements in Flash Builder. But, that is probably not going to happen. Catalyst was our bet and it let us down in a large way.

 

Illustrator support for Symbols as MovieClips/Graphics is a start in that direction. I realize print guys will think its all superflous fluff so maybe offer it as some sort of addon for web oriented folks. Right now GUI design in FLEX could be sooooo much smoother in the truest CS5 mantra. I'll concede that Flash Builder 4 has grown leaps and bounds in that direction but we've still got a long way to go.

Promotes

Demotes

No evaluations ready
Recorded Outcomes
Record an Outcome