I often talk about the important role visualization plays in my work. I personally don't really understand things until I can see them. One example of this that I showed at FitC this year was the SparkTable tool I use to visualize and compare easing equations. It's very simple, but I've found it very useful when trying to choose between two similar eases, such as a quintic versus exponential ease. It's also very handy when developing custom easing equations.

Simply queue up a bunch of easing equations to test, then sit back and watch the results.

It seems like every UI design we are asked to implement these days has what I call "designer scroll bars" - skinny little tone on tone scroll bars that have no scroll arrows. While I'm not a big fan of these scroll bars for a number of reasons (not least of which is usability), they are still something we're required to do on a fairly common basis.

Luckily, in Flex 3 hiding the scroll arrows, and making the scrollbar thinner is a fairly simple task that you can accomplish globally with just a few lines of CSS.

We've been getting lots of questions about why gProject has not been updated to support ActionScript 3. Until now I have not been in a position to respond appropriately, but today I'm happy to announce that Adobe acquired gProject late last year. Since then, we have been working with the Flash team to completely overhaul the panel for AS3, add new functionality, and significantly improve the interface.

As a result of the Adobe acquisition, we will no longer be developing gProject and have deprioritized our support for gProject as a product.

We will continue to offer gProject for Flash 8 and CS3 for the immediate future, but it will not be updated further. The product page for gProject and panel pack will be updated immediately to reflect this.

If you purchased gProject in the past 3 months, and have any concerns, please contact us through our support form.

During the course of developing the Spelling Plus Library, and more recently while adding multilingual support to it, I discovered two serious bugs with the Regular Expression implementation in ActionScript, and how it handles accented characters.

First, RegExp in AS3 does not include accented characters in the word character class. For example, the pattern /\w+/ (match one or more word characters) matches "r" and "sume" in "résume", when it should match the full string. UPDATE: Arthur has pointed out in the comments that this is correct according to the ECMAScript and POSIX RegEx specifications. \w is intended to match just the set [a-zA-Z0-9_] , which it does in AS3. With that being understood, it would be nice to have support for unicode property sets (which allow you to match word characters in any language, among other things), but I can understand that this may have an unacceptable impact on the size of the Flash Player.

Secondly, there is a somewhat obscure problem with how the Flash player matches \S and accented characters. Specifically, it appears that it does not count accented characters properly when matching them to \S, and this results in weird results. This is not the case with the negated whitespace character set [^\s], although these sets should exhibit identical behaviour in RegEx. This issue is pretty weird, so I'll give a few examples:

1. the pattern /\S+/ (one or more not-whitespace chars) will match the full string of "é aé", when it should match "é" and "aé" separately.
   
2. the same pattern /\S+/ will match "aé" and "bé" correctly for the string "aé bé".
   
3. the pattern /\S{2,}/ (two or more not-whitespace chars) will match the full string "aé bcé" when it should match "aé" and "bcé".
   
4. the same pattern /\S{2,}/ will only match "bcé" for the string "éa bcé", when it should match "éa" and "bcé"
   

Hopefully this is helpful for other people working with RegExp, especially with languages other than English. It is quite frustrating to work around - I ended up writing a specialized character lexer instead of using RegExp in SPL.

Know of any other RegExp bugs in AS3? Share them in the comments.