I've realized that every dev team is different, so I can only speak from my experience. Typically I'll do the UI design, layout the app in MXML and then apply the appropriate skins. If there's some custom component work, or something that goes beyond what you can do with Flex's out of box stuff I hand it off to someone who specializes in that. I go over the design with the developer and mention I want x,y and z styleable. Once that's done I go in and approach it just an out-of-box component.
Right now, some of the automation between CS3 apps and Flex are still kinda rough around the edges, but I have a feeling Adobe is going to be addressing some of the frustrations and/or questions people have pretty soon (I hope). If I do use some of the automated stuff I usually go through and organize things the way I like it. I know at MAX there's a few sessions around this topic and I've blogged about it in the past: http://scalenine.com/blog/2007/02/26/app-skinning-a-workflow/ Not sure if that helps. Juan scalenine.com degrafa.com --- In [email protected], "vic8427" <[EMAIL PROTECTED]> wrote: > > My company and I(developer) are beginning to use Flex more and more > and want to solidify a better process between designer and developer. > The first project's workflow ended up with the designer creating a > really intricate design in Illustrator, with tons of layers and what > not, and handing off that file to me. Skinning was a nightmare to me > as a new Flex developer. After reading this article on Adobe's site, > http://www.adobe.com/devnet/flex/articles/flex_skins_04.html it > appears to me the typical handoff is a file of library objects with > all the different skins of all components used. This seems like a > great solution for a developer, but not a typical approach that a > designer would take or even be comfortable with. > > I just want to gain insight into other designers/developers workflow. > (typical handoffs from designer to developer, how developers > approach implementing designs) >
