F*CSS is a finely tuned instrument but sometimes it is helpful to see just how fast the parser can index and access CSS selectors. To help you better understand the impact F*CSS will have on your project I am happy to release my F*CSS Performance Tool. You can use the following tool (which I have run on all of my own projects) to test the performance of a rather large StyleSheet or supply the url to your own StyleSheet. I am always interested in seeing how F*CSS performs on your computer so after you run the test, please send me an email of the output along with the specs of your computer- fcssspeedtest at flashartofwar dot com.
It is important to note that not every StyleSheet will work out the gate with F*CSS. Although the CSS used by F*CSS is very similar to it’s HTML counterpart, F*CSS is really geared for pubic properties on AS3 class instances. Complex Div, P, and other tag styling will either be ignored completely by the parser or break the rest of the selectors. Consider yourself warned!
*Tidy refers to a Regex pattern F*CSS uses to strip out white space and condense the StyleSheet before parsing. This process is the most intensive part of indexing the CSS but must be done to make sure the CSS is as optimized as possible. In F*CSS you have the option of flagging a StyleSheet as being pre-tidied or needs to be tidied. Doing this process on the server will greatly improve the performance of F*CSS’s parser and the time it take to index a StyleSheet.
