There is actually some buzz around the 60 frames per second draw rate limit fixed by browsers to Flash player. All the noise cames from the bubblemark benchmark that is intended to compare performances of different plug-ins while playing an animation at the maximum speed they can. The only result we get with this test is there is a limit fixed by browsers to the draw rate of plug-ins. Everybody is agree to said that results of this test are distorted.
«Working sets» is an underused Flex Navigator functionality that could save you a lot of time when your Flex workspace contains many projects.
As its name says, it allows you to create sets of Flex projects to work on. The magic is that when a «working set» is selected, Flex navigator only shows projects related to this set. You could access all your classes and files in an instant.
It is not as cool as Java navigator filters (implemented in Flex navigator but not working) nor as Eclipse switching workspace that could share the same settings (not implemented yet), but it does its job when needed.
I will show you how to configure the whole thing.
Two weeks ago Oliver Goldman from Adobe wrote a post where he reveals that the warning about installing an Air application will stay in the next version, even if you choose to publish an application that do not access the user file system.
I personally think that this will tarnish the reputation of Air. I so have asked him in a comment why not display the warning before the application asks to access the file system, while offering at the same time an option to ask to never display this warning again. Surprisingly Oliver reacts to my comment in a second post. All I can say is that he doesn't like the "just in time warning" solution. 🙂