When you copy the CSS from the style explorer you'll get something like this:

ToggleButtonBar {
   buttonHeight: 41;
   buttonWidth: 109;
   buttonStyleName: "mytoggleButtonBarButtonStyle";
   firstButtonStyleName: "mytoggleButtonBarFirstButtonStyle";
   lastButtonStyleName: "mytoggleButtonBarLastButtonStyle";
   selectedButtonTextStyleName: "mytoggleButtonBarSelectedButtonStyle";
}
 
.mytoggleButtonBarButtonStyle {
   highlightAlphas: 0, 0;
   fillAlphas: 1, 1, 1, 1;
   fillColors: #333333, #333333, #ff9900, #ff9900;
   color: #ffffff;
   textRollOverColor: #ffffff;
   textSelectedColor: #ffffff;
   themeColor: #0000cc;
   fontSize: 14;
   fontWeight: normal;
}
 
.mytoggleButtonBarFirstButtonStyle {
   cornerRadius: 9;
}
 
.mytoggleButtonBarLastButtonStyle {
   cornerRadius: 9;
}
 
.mytoggleButtonBarSelectedButtonStyle {
   color: #ffffff;
   fontSize: 14;
   fontWeight: normal;
   fontStyle: normal;
   textDecoration: none;
}
 

What I found is you need to copy the styles from the .mytoggleButtonBarButtonStyle class to the other styles that are generated for you. Obviously keep in mind that you only want to copy the properties that are going to be the same for each state, otherwise you'll overwrite your changes. This worked for me, hope it helps.

My latest article is up at InsideRIA. It's titled, "RIA's go Hollywood: An Introduction to Integrating Video Into Your Application." It provides an introductory look into how to best incorporate video into your applications. Special thanks to Josh Reed from Reed Multimedia for helping me out with shooting and editing the video.

A Flex Developer's Guide to User Experience Work Flows and Best Practices

Albert Einstein put it nicely when he said "Make everything as simple as possible, but not simpler." This is an important adage to keep in mind when we're designing and developing our applications. We're all painfully familiar with the concept of scope creep.  Where the scope of a project gradually increases and before you know it, it has become unmanageable and impossible to complete on time or within budget. There is a similar concept known as "feature creep" where features keep getting added to an application because "oooh, that would be cool," or "that would be nice to have too." Often times we're our own worst enemies in this regard. We've just learned a new technique or about a new piece of technology that is available and we just have to use it! The problem is, if the feature isn't essential to the core function of the app it's just noise. Something to get in the way and confuse our users. Take a look at Google. When they started out they were just a search engine. When you went to google.com there was no question what you were supposed to do. One box, one or two buttons and you were off. Simple, efficient, and it got the job done.

80% of users are what as known as "perpetual intermediates." Basically this means that they quickly progress beyond the beginner stage of using your application to the intermediate stage where they have a good grasp of how to use the tool to get their job done. Very few will progress to the "advanced" user stage. So, rather than spending valuable time and resources on developing features that few, if any people will ever use focus that energy on a select few features that will help your users achieve their goals. Center your efforts around making those features as simple to use and as effective as possible. People don't rave about a program because it has hundreds of features, they rave about applications that help them achieve their goals in the simplest, most efficient way possible. Keep it simple.

Download

Mac: user/Library/Preferences/TweetDeckFast[bunch of numbers]/Local Store/

Windows: C:\Documents and Settings\user\Application Data\TweetDeckFast[bunch of numbers]\Local Store\

It's not ideal, especially if you make a lot of changes to your settings but it's better than nothing.

UPDATE: A reader just informed me that you may need to change the files permissions from 'Read Only' on the DB file before you can update the DB file on the machine you are copying to.