Grant Skinner

The "g" in gskinner. Also the "skinner".

@gskinner

The Internet is sh!t

Via gijs nijholt

I don’t usually link to people’s opinion pieces, but I thought this post on why the Internet is shit was a good read, and the last paragraph reflected a feeling that plagues me.

When I first got into web design (a whopping 9 years ago), everything was new, everyone was excited, and I was kept in a constant state of awe as the modern “rich” internet emerged from the primordial soup of HTML 1.0. Maybe I’m just getting old and jaded, but lately that awe has receeded – I rarely see web work anymore that really excites me. There have been a few pieces that really caught my attention as good examples of what can be done (really, what should be done), but nothing that makes me really feel that the pea-brained dinosaurs of the present-day web will be replaced with smarter, more adaptable successors.

I’m left in a constant state of anticipation – I feel like something has to happen, some new concept has to begin defining what the web is going to be 5 years from now. This serves to define much of my professional life, I’m fortunate in that I can usually pick and choose the clients I work with, and I typically do so on the basis of how progressive or interesting the project (or the client) is. It also drives me to tackle monolithic projects with little hope of recompense, just to prove to myself and the community that things can (and should) move forwards (see: FlashOS, FlashOS2, gModeler, etc).

I think the most exciting thing I’ve seen recently is the involvement of talented writers, with a firm understanding of the medium, in the development of websites. A good writer goes beyond copy-writing to help define the narrative of a site, establish a repoire with the user, effectively (and engagingly) communicate the core messages of the site, and work with the designer to develop the user experience.

Now don’t get me wrong – I love my job, and I think the Flash community is phenomenal, I’m just left wondering if there isn’t more that we could do to evolve this medium to the benefit of our clients before the meteor (longhorn?) hits.

PS. If you’ve built a Flash intro in the past 3 months, without discussing with your client why its a waste of their money and what their alternatives are, kindly raise your hand and exit the blog – you’re holding us all back, mate.

[EDIT:] Wow, I really must be getting old and cranky… too many complaining posts in the last few days… must… post… something… positive. 🙂

FLAws: FP7 drops click events

To begin the FLAws series, I’d like to shine some light on what looks to be a major Flash Player 7 bug. This issue has had Beau and I ripping our hair out for the past few weeks, as we have sought workarounds for it.
Description
In short, Flash Player 7 will sporadically fail to register Release events under high strain situations. This causes huge problems, as users must click buttons and components multiple times before they will register the click – talk about a usability nightmare.
Read on for a more in-depth description, and the workarounds that we found.
Continue reading →

FLAws: Prologue

Recently, I have been working on a number of interesting projects that have allowed me to really test FlashMX 2004 as an application development platform. While I am very happy with the workflow improvements in the new version, I have also encountered a number of fairly large flaws that can make developing applications in F04 a migraine-inducing experience. Because of this, I have decided to start a new series of posts called “FLAws” (oh how witty), which will outline these issues as I encounter them.

My intent is not to just bitch about these problems. It is to raise these problems in Macromedia’s collective consciousness, and to help others avoid the same headaches by providing suggestions and work-arounds. I also welcome input from the community – if I get something wrong, you have a work-around to share, or you have discovered a problem I haven’t mentioned (please research it thoroughly first), please drop a note in the comments.

I suppose the first of the FLAws was really the EULA issues, which are still outstanding, but I think I’ve covered those well enough (at least for now). I will be making my first official FLAws post later today with a description of a Flash Player 7 bug that has caused us a lot of grief, and some workarounds.

Blog Spam Update

I don’t know if everyone has seen a huge decrease in blog spam, or if my simple blog spam counter-measures have just paid off, but it’s way down for me. In fact, I haven’t received a single piece of blog spam in over a week now.

Besides the technical changes I made, I’ve also been deleting spam within minutes of it being posted, which hopefully helps to deter manual spammers over the long run, as they realize what a waste of their time it is.

setStyle == Huge CPU drain

Sam Neff recently explored how setStyle notifies components of style changes, and the results are definitely worth noting (this may save you some major headaches, so listen up). It seems that every time you call setStyle, it calls notifyStyleChangeInChildren(), which iterates through EVERY movieclip in your movie, checking to see if it should notify it of the style change… ouch! Double-ouch even.

This was very useful information for me, as I’m presently working on a (top secret) project that has 100+ components instantiated at a time, and I was a little confounded as to why initializing the first interface was taking about 12 seconds. It all became very clear when I realized that I was setting about 40 different styles, which resulted in literally TENS of THOUSANDS of movieclip “style checks”. Moving the setStyle calls to the first frame solved the problem completely.

The moral of this story: always set all of your global style information before instantiating ANY movieclips, and then don’t change it – at least until Macromedia changes their EULA, and someone can legally distribute a fix for it (jab, jab). 😉

‘Tis the season: Snow FLA

Well, the -20c temperatures (that’s -4f for those of you stuck with archaic systems of measurement), and 20cm+ of snow (8″) we got over the past week tells me it’s about time to dust off the old snowflakes code, and make it available to the community. There’s a lot of code available for simulating snow, but I think my extensive real-life experience (brrr!) gives mine an edge, plus it comes with a cute peacenik snowman.

This is the same FlashMX version that’s been available on my site for a year and a bit now, with a few minor modifications. I plan to post an MX 2004 class based version, just for the helluvit, in the near future.

You can take a look at the Flash snowfall swf, then download the free FLA. Peace on Earth, and goodwill to men. 🙂

Also, here’s a nice (though completely uncredited – Oscar, you bastard! 🙂 usage of my code with some nice snowflake artwork tossed in.

FlashMX 2004 Enterprise-level Development

My apologies for the lack of posts lately – things have been comfortably busy, with client projects, and a few other endeavours, one of which is a new advanced Flash course I will be instructing at the Northern Alberta Institute of Technology (NAIT) in January and February ’04.

If you’re an intermediate Flash developer in Edmonton or area, check it out – it might be “the course to take your game to another level”. It also helps that NAIT is running it for an amazingly good price.

Read on for the full press release from NAIT…

Continue reading →