As rapidly as internet technology is said to progress, it still seems like the framework for content delivery is mired in the era of text-only pages being shuffled from one university to another. Like it or not, the web is now a multimedia-rich environment, and its structure should change to accommodate this. The W3C, however problematic, is still a great standards body and deserves ISO status. Web standards are desperately needed, but progress has been too slow. Too often, good ideas stagnate (sorta like gnu ones). Maybe we need to “think outside the box” to move things along. Here are my own radical ideas for the web:
On-the-Fly Font Distribution System
When a job is professionally printed, great pains are taken to make sure that the printer has the necessary fonts. If this was not done, then layouts would only contain the dreaded courier default. Now imagine that every printed piece you ever laid eyes on contained the same 2 or 3 fonts. Deja vu? The world wide web allows easy transfer of text, and an HTML file can specify the font used to render it. But we resign ourselves to using ubiquitous system fonts: arial, helvetica, geneva, etc., or else our text reverts to the user’s default. The only way to break free is by embedding text in an image or a flash movie (or some other back-door solution). These practices are SEO suicide, however, as we need searchable text for SE bots to read and index. My proposed solution? Do as flash does! Send the browser a compressed file containing only the characters needed to render the page (or the whole alphabet when needed; ie. forms, dynamic content). Then add a link to said file in the head section, and voila! Text that is beautiful and searchable.
Template file
This would work like a style sheet, only with content. Instead of style info, classes would contain text, images and other content. If you’ve ever used Dreamweaver, you know why this is a good idea. The user would download repeated content only once, and it would be stored in the browser cache. You could change content site-wide by manipulating just one file! As I say, just like style sheets, but for content. Just come up with an XML-based file format, and we’re good to go with this one.
SVG & SMIL
I know, I know; not my ideas, but we desperately need a new way to jump-start these formats. It ain’t gonna happen on its own, folks. Here’s my solution: Start a group dedicated to developing quality freeware SVG and SMIL editors. The W3C should sponsor and fully endorse this. Illustrator exports SVG just fine, so SMIL’s the biggie here. Let’s face it: we need a program that is to Flash what Gimp is to Photoshop. A huge, wonderful Flash-like program that edits SVG graphics, creates tween animation, edits sound files, works with bitmaps, utilizes something akin to actionscript (javascript? LOL!) with a GUI like Flash’s. Layers, keyframes; the whole 9 yards. This will finally bring down Flash, since that’s what all you standardistas want. I love Flash and stand by it, but I’m telling you: this is how you bring down Goliath. And I’ll reluctantly admit that the internet will be better for it.