The concept is simple. Improve workflow between designers and developers. Ever since I can remember, everyone always talked about improving this relationship. Get designers to do more towards project setup than they normally would be accustomed to, without having them type a single line of code. The reasoning behind this is simple because it is not always possible to technically implement the design. The only alternative is to manage expectations or at least that was until now.

It is important to know what kind of tracking exists as you might just be in a tight spot one day being asked to implement tracking of some sorts. While this isn't rocket science - going back and forth between your company, the tracking vendor and the client can quickly snowball hours into days.

Saatchi & Saatchi did this site to illustrate even more my point about Flash and the South African corporate market. It's a start init?

Offers you a low and high bandwidth upon entering. Didn't remember my choice but that would be a nice-to-have. Looks like a normal site, acts like a normal site but it's Flash. Not bad. A little bit like like Savannah, "It's dry but you can drink it".

http://www.107.co.za/

I stumbled upon this gem in the Flex API about the intensity of the setStyle() method on processing. I only recently had the need to use it and was quite shocked at how slow this actually was. Granted I used it on a Datagrid which is probably not the best idea but I'm a bit of a if-it's there-then-use-it-kinda-guy.

Joan Lafferty blogged about the upcoming changes in Moxie for setting component and sub-component styles. Very insightful article. It immediately made me ask the question. How does this impact the setStyle() method. Presumably the "StyleProxy" should alleviate this problem as you have more control over what style is set to what component, regardless of the hieracrhy.

See the warning in the Flex api here »