Tue 9 Oct 2007
Skinning/styling features in Flex Builder 3
Posted by Narciso Jaramillo under design | Flash Builder14 Comments
“Well,” you may be saying, “Thermo looks great and all, but what do I do in the meantime?” The good news is that we have some nice improvements coming in Flex Builder 3 that help automate the visual design workflow, and you can try them out in the Flex Builder 3 beta that we posted to Adobe Labs last week.
In Flex 2, if you wanted to style components using CSS, you could use the Flex Style Explorer to experiment with the styles, then cut and paste the CSS into a Flex app. If you wanted to skin components with custom graphics, you could use my Developer Center article on creating skins using the Creative Suite tools, but you would likely still need to edit some of the CSS by hand.
The new design features in Flex Builder 3 help automate both of these workflows. Here’s a quick summary:
Flex Skin Design Extensions for CS3. These actually aren’t a feature of Flex Builder 3 itself, but rather a set of extensions for Photoshop, Illustrator, Fireworks, and Flash that make it easy to create skins for Flex components. Essentially, we’ve taken the templates from my Developer Center article and integrated them into the CS products through a “New Flex Skin” menu command in each tool, adding the ability to create individual component skins as well as a whole template, and to create multiple variations on a single component. We’ve also created a one-step “Export Flex Skin” command for PS/AI/FW that automates the manual export steps from the article.
You can download beta versions of the skin design extensions from Adobe Labs. Thanks to Juan Sanchez of ScaleNine for building out the new templates for us!
Flex Component Kit for Flash. For Flash, we’ve gone one step further, and redone the skin template entirely to use multi-state symbols using the Flex Component Kit for Flash. If you’re not familiar with the Kit, it allows you to build components and skins in Flash that can be used in Flex applications–participating in layout, sending and receiving events, building states and transitions on the timeline, and more. In the case of skins, this means you can build animations between the different states of a component–for example, between the up and over states of a button–using the Flash timeline.
Import Skin Artwork. In my dev center article for Flex 2, we provided a pre-built CSS file that worked in conjunction with the skin templates to glue the template artwork into your Flex application. If you wanted to create multiple variations of a component, you had to do this by hand, and if you wanted to only skin certain components, you’d need to edit the CSS file manually.
In Flex Builder 3, we’ve automated this process with File > Import Skin Artwork. Now you can just point at a folder of bitmaps or a SWC exported by the CS3 skin design extensions, and Import Skin Artwork will automatically write all the CSS code to glue those skins into your app. You can even create multiple styles for a given component using the CS3 “New Flex Skin” commands, then import them as separate CSS class styles. And if you have fully custom components that expose their own skin properties, you can build skin templates for those components that can be imported using Import Skin Artwork by following a simple naming convention.
CSS Design View. This is really the heart of the new design features in Flex Builder 3, and it works with both the skinning and styling workflows:
- If you’re following the skinning workflow from the previous features, then the CSS Design View will let you visually customize things like font styles and scale-9 grids for the imported skins. Previously, you had to do this by hand in the CSS.
- If you’re doing pure styling, you can use the CSS Design View like a beefed up version of the Flex Style Explorer, to create global, component, or class styles, preview them directly in Flex Builder, and write the code directly into your Flex application.
Accessing the CSS Design View is simple–just open any CSS file, then click the “Design” button to switch to Design View.
If you want to see some demos of these features, here are some resources:
- We showed off a number of these features at Flex Camp in SF a couple of months ago; you can watch the videos of CS integration and skinning workflow (boy, I hate the sound of my voice in this video!) and CSS Design View and other FB3 features. (Update: forgot to put in a link to the second part of this originally.)
- The Flex Builder team put up writeups and video of Import Skin Artwork and the CSS Design View (but not the CS3 extensions or the Flex Component Kit for Flash).
- Peter Flynn also gave an excellent talk on this topic at MAX, but there’s no video of that up yet–I’ll post a link when it becomes available.
Download the Flex Builder 3 beta, give the new features a try, and let us know what you think!
digg this |
del.icio.us | 14 Comments
[…] Some of these things may or may not affect some of the previously released ScaleNine themes. Moving forward, the themes I create will be built for use in Flex 3. I’ll try to add to this list as I notice more things or as others let me know of what changes they’ve noticed. Be sure to check out Narciso Jaramillo’s post on some other workflow features that are available along with the new Flex Builder 3 Beta 2. […]
[…] I never really thought about getting credits on a piece of Adobe software, but it’s definitely cool to see (middle, right). Yes, I realize my name is a common one, but I swear it’s me. In case your wondering what I did, you can check out NJ’s post for some insight. […]
Cool stuff, thanks for the info and links.
[…] ? Flex 3 beta 2????????? ????????? ????? ????????????, ??? ??????????. ?? ???? ??? ?????? Juan ? NJ. ?? ???? ????? ?????? – ???????? ?????????? ??? Flash. […]
Hey,
Loving the new changes, they really do help! One issue i’ve found, and it might just be me not being able to figure out how to address it properly, but i run FB in eclipse as a plugin, i also run the plugin oxygen for XML editing. oxygen has a CSS editor, even with FB set as the default editor for CSS, oxygen somehow is not letting the css design view work. Only way to see it is through disabling oxygen which slows my XML editing process. Maybe i’m not just not familiar with something in Eclipse i need to be doing, but this has been a pretty big issue for me.
Hey James–not sure what’s going on there, but I’ll check with other folks on the Builder team and see if they know anything about this.
nj
By the way–when you run into issues like this, please log them as bugs in the open Flex bugbase:
http://bugs.adobe.com/flex
Thanks!
Spoke too soon–it’s already in the bugbase ๐
https://bugs.adobe.com/jira/browse/FB-9250
I am fairly new to using Flex and, as a designer, it can be somewhat intimidating. (Can’t wait for Thermo!) But, I have to say that your Flex Skinning article and the templates you created have been fantastically helpful. Thank you for putting it up!
PS: I am trying to convince my team to switch to Flex Builder 3, any tips?
@Mathilde—glad you’re finding this stuff helpful! For Flex Builder 3, I guess it depends on what your team values most, but I would say that aside from all the features for improving the skinning and design workflow listed in my post above, we’ve also added a lot of productivity enhancements on the developer side:
— Refactoring for intelligently renaming variables/methods/classes
— Automatic creation of bridge code for web services (WSDLs)
— Integrated support for building AJAX bridge classes, so your Flex components can talk to the JS in your web pages
— Profiler for memory usage and performance, so you can figure out how to make your Flex app run faster
— Support for building Adobe AIR apps
— Framework caching, so users only have to download one copy of the framework once no matter how many Flex apps they visit
And probably lots of other stuff I’m forgetting ๐ More details are on the Labs page about FB3:
http://labs.adobe.com/technologies/flex/flexbuilder3/
[…] selfish, and it’s my job to be critical; things can always be made better. …like having gems like this not be hidden on some awesome employee’s blog, and rather trademark features of a product […]
I’ve found the information you’ve provided very useful – thanks! As a designer I am also intimidated when it comes to using Flex. Being able to switch to design view for the css is very handy – except it crashes a lot when I do that. Have you found that to be the case for you too?
@Chris: Sorry you’re having problems! Have you updated to beta 3 of Flex Builder 3? If not, you can download it here:
http://labs.adobe.com/technologies/flex/flexbuilder3/
If you’re still getting crashes with beta 3, it would be great if you could file a bug with the CSS file that’s causing the crash:
http://bugs.adobe.com/flex/
Thanks!
[…] http://www.rictus.com/muchado/2007/10/09/design-workflow-features-in-flex-builder-3/ […]