Technologies
Post Idea
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
invite
This Idea is hidden. Change Visibility
Shouldn't "Convert Artwork to Component" be "Convert Artwork to Skin"?
(D2389)
3
Vote Score
Submitted:
11/07/2010
Status: 
New Submission

Catalyst can be pretty misleading on the subject of component skinning.

 

"Convert Artwork to Component" kinda implies that it's gonna convert your artwork to a component. Looking at the code reveals that's exactly what it doesn't do. In fact what it does is convert the artwork to a "spark" skin class. As far as I can tell the only way in Catalyst CS5 to actually create a component is when you "Convert Artwork" to a "Custom/Generic Component". In this case it converts the artwork to a stateful component (and doesn't create a skin). All very misleading.

Promotes

Demotes

No evaluations ready
Recorded Outcomes
Record an Outcome