No Clean Feed - Stop Internet Censorship in Australia
«
»

Flash

Over-engineering

05.15.08 | 4 Comments

Yesterday a colleague from downstairs (where .NET folks huddle in the dungeon-like darkness and pretend to enjoy using Visual Studio … unlike on my floor where designers and Flash devs flit about in a world of sunshine and butterflies) asked me to make a very simple little SWF … just a marquee basically, similar to the Windows “Marquee” screensaver with text scrolling past and wrapping around.

I approached the job with totally the wrong mindset. I wrote classes, and an XML schema, and planned on making the text fields dynamically generated on-the-fly and to read in a stylesheet, and the text from an XML page. Then I started thinking about how different amounts of text would change the size required for the TextFields – and how I could relate that to the SWF – which should, of course, work on a variety of screeen sizes …

Luckily at that point I went to the cafe and got a large latte. Under the effect of the caffeine I realised the obvious truth: I didn’t need flexibility, extensibility, or to attempt to solve a whole class of marquee-style problems. I just needed one five-minute job with named stage instance TextFields and a single document class (not timeline – even in a hurry there are some depths I won’t stoop to). Hard coded text. Ta-da, problem solved, and didn’t distract me away from my main project, a big 3D-based Flash site.

Classic sledgehammer-nut scenario. Sometimes you just have to forget all your good habits and knock something together …

related

4 Comments

have your say

Add your comment below, or trackback from your own site. Subscribe to these comments.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

:

:


«
»
Close
E-mail It