Falling Leaves: the Ardes blog

Archives filed under "javascript"

Higgar Tor Panorama

Ray Drainville

A picture from a few weeks ago:

This was an interesting experiment. Readers many know that I’ve made a lot of virtual reality panoramas over the years. Given the rise of portable devices such as the iPhone & iPad, however, is requiring a re-think of how we present them: browsers on portable devices don’t support any plugins. The examples in the above link require Quicktime, which is just as forbidden as Flash. It looks like the only option is Javascript-based interactivity, which will require some serious testing.

So why is the above picture an experiment? Well, because instead of using all my VR photographic kit, I used an iPhone & Debacle Software’s Pano, which does a really nice job for casual picture creation. You can’t, so far as I can tell, make a complete 360-degree panorama. Perhaps that’s coming, though.

Shape Type

Ray Drainville

Hot on the heels of Kern Me is Shape Type—by the same people, incidentally. This type, you test your abilities to design type as well as the masters who made the fonts in the first place:

[

My mind is thoroughly blown by this. It’s another tour-de-force of HTML5 programming. Like Kern Me, Shape Type is an amazing use of the canvas element. Who knew that you’d be able to replicate Illustrator’s vector-editing environment in a web browser? Not me.

Kern Me

Ray Drainville

Type nerd? Appalled by keming? Then you will really love the Kern Me game.

This is an inspired bit of coding, spectacularly well done. And not only do you use your left & right arrow keys to shift the letters, as in standard typesetting apps. To increase the amount of shift, and totally without thinking I held down the ‘shift’ key while using the arrow keys, and that works, too!

The Universe in Chromoscope

Ray Drainville

The University of Cardiff’s Chromoscope is a fantastic way to visualise different wavelengths—visual, x-ray, radio & more—in the universe. Use the slider to see the differences: you start to see some of the interactions between them.

Javascript Won’t Save U After All

Ray Drainville

In the past couple of months, two authors whom I admire have renewed interest in Dean Edwards’ confusingly-named IE7 script—a Javascript hack that makes Internet Explorer version 6 behave more like a standards-conscious browser.

The very title of Eric Meyer’s article—“Javascript will save us all”—suggest that we’re about to enter a golden age in support for the seven-year-old browser. And Jeremy Keith has recently advised people how to gauge when to use the IE7 script.

Well, I don’t know about you, but to me, this is more than music to my ears, it’s the equivalent of Bach being played on a glass harmonica right next to a chocolate fountain. But years of struggling with IE6 have hardened my defences. Since using Meyer’s CSS zero reset I’ve had great results with IE6—but only from the beginning of a site design I hasten to add. As I’ve written earlier the reset does little to fix a pre-existing design.

Dean’s script has popped up now & again over the years to tempt me again & again with its promises. But it’s nowhere near as well-known as you’d expect for something that gets such high praise from some very astute authors. Why is that?

Well, it might be because it doesn’t really do what you hope. It’s certainly nothing like a magic bullet. In fact, I’d recommend that you stay away from it. Why? Because you’ll have to go through the hard work of declaring a separate stylesheet for IE6 anyway: adding another script to the mix just adds more to the confusion of figuring out why something doesn’t work.

Both Edwards’ script and Keith’s recent article popped into my head because recently we’ve been working on the site of one of our favourite clients. In the course of making the site more amenable to search engine optimisation, it became clear that we should revisit the CSS of this, the last site we developed without the CSS reset.

Now, it might seem like I’m cheating in the above examples: I removed the painstakingly-tweaked IE6 CSS when I introduced Edwards’s script. But I’m not. If I were to follow Meyer’s & Keith’s advice & used the IE7 script as a basis for my IE6-oriented work, I’d have a hell of a lot more tweaking to do, plus I’d have to cope with the rigmarole involved in dealing with someone else’s script.

So, take some advice: if something looks like it’ll magically solve all the problems that have consumed years of painful work, don’t bet your reputation, or your schedule on it.