www.newmediaaward.com

So i've completed the first ever hyper-hardcore-coded interactive Flash website under my hand, but the real pain in my head is, it's ultiamtely CPU intensive that rendered me speechless when it ran on Mac, slow as a rock.

Well, i would still like to share the ups and down throughout the project itself and few discoveries I found and made within the project.

Some basics one, it's best you never user wmode=transparent for good god's sake, you'll end up scratching your head fighting for compability across platform and browser, that is when i realize it is not supported in Mac, and even worse, it increases the lag/cpu hogging. So when i switch back to an opaque background instead for the site, i'm still pondering on how i can stretch the background that is textured to look right on 'designer' point of view instead of splatting a flat colour background on it, it's a real pain, really.

So then i've started to study how it is made posssible that all these interactive sites nowadays, made full use of FSF (Full-Scale-Flash) which stretched the entire flash to 100% width and height, that covers their entire browser and doesnt scale the movie whenever i resize the browser's window instead it only moveis it position and maintain it at center.

That is when something like Stage.align really saved my ass from all the trouble. But as soon i got happy and uploaded the site, i'm bound to another tragedy that the size only loads half on Firefox, i keep on cursing and found out that there's a runaway for it, to add a bit of CSS code on top of your page.
height 100% for your body,html

So that really pissed me off, living thinking when there would be a day that browser war stops. But it's not the end yet, after spending restless month developing the site and figuring out this and that, I've chosed to use only 100% for the width of the class while maintaining the original height of the Flash without stretching it to 100%, because it doesn't fit correctly/entirely inside a 1024x768 screen resolution and would crop my project into half. God.

But alas, it's online and up at http://www.newmediaaward.com. The only pain left to me is to reduce the cpu processing cycles within the site, because even on idle, the movieclip's onClipEvent are everywhere and hogging up all the processing power.