But I would propose something different entirely. Instead of using a js library to help browsers properly render a soundly constructed html5/css5 webpage, short of making sure it doesn’t look like “total ass” on IE, just let the page render as it lay.

By now, web designers are largely aware of the rendering quirks of various browsers. Little things like not adding margins to floating divs for IE’s sake, or not applying -webkit gradients to divs that contain text fields, are a part of mental mine field map that goes into our work.

Using a javascript library to get around this isn’t the answer. Remember that script that lets IE6 properly render PNG transparency? It might have been relevant to a couple of years ago when there were still a vast majority of users that used IE6, but most web designers have abandoned even trying to support the browser, much less trying to make every pixel line up properly or make every image look decent. At some point (if our bosses let us), we move on.

Sadly, we moved onto other scripts that do what html5 is supposed to do already.

Here’s my advice. Write your site to work just fine without any javascript (or css for that matter) needed. If you can still use the site, you’re good to go. Using ajax history to browse back and forth with the browser chrome? Make sure it works without javascript and move on. If you’ve got some killer CSS mojo for your site, just write it. Write that widget that does that thing with the stuff, but to say that we have to cover every contingency is unreasonable.

When did we go from saying “to hell with bad browsers” to using libraries to keep these browsers on “the same page?”

Older browsers won’t go away (I still see Netscape occasionally show up on Google Analytics), but the support we give them can.

I like to look at these barbaric browsers like the Klingons in Star Trek XI. Their survival was in jeopardy and Kirk was having none of it. Eventually, he came around and now we’re stuck with the Klingons and their foreheads forever.

Don’t let this happen to bad browsers. Let them die.

1. Links

• Stop Forking With CSS3
• Taking Advantage of HTML5 and CSS3 with Modernizr

Bookmarklet

Someone on twitter asked how to find and replace certain words on a web page. This is a bookmarklet on that replaces the word ‘god’ with ‘sky cake.’

Test it out!

The Variants is a new web series sitcom about the crew of a local comic shop. So far, four promos have been produced and released in time for SDCC 2009 and Episode one is scheduled for release. Each episode (or is it webisode) runs about ten minutes.

Putting this together was a lot of fun. With internet video content rising well beyond YouTube, I had many examples of what people expect from a media web site. Plus, I got to work in a little bit of html5 semantics.

Go watch The Variants promos and laugh, laugh and laugh.

Scribbr is a tiny web app for drawing and posting to twitter. With jQuery, the user can control the color, size, opacity of the cursor to draw on the canvas element 320 x 320 in size.

Last summer, I had the opportunity to work with Eisner Award winning cartoonist Scott Kurtz of PVP. During one conversation we had, he came up with a punch-line to what we were talking about. I don’t remember what the subject was, but the punch-line involved a mock editorial cartoon. He grabbed a 2″ x 2″ sticky note pad and drew the cartoon. We had a laugh.

This would never happen online. At least, not in any convenient, simple, method that I was aware of.

Right now, it’s very crude. The controls are, admittedly, non-intuitive. There is no ‘Undo’ other than clearing the canvas and starting over. It doesn’t support older browsers either.

I’m actually quite okay with that last part. This site was immensely fun to build. Getting it to work on IE6 would have taken away from that. Right now, I know that it works on FireFox 3.0, Safari 4.0b (or WebKit nightly build), and Google Chrome 2.0.

Zeus Comics new design went live Thursday

If for no other reason than finally consolidating the past five years of css style changes into some semblance of organization, this redesign was a long time coming.

Zeus Comics and Collectibles is an award-winning comic book retail store in Dallas, Texas. For almost nine years, Zeus has been serving the needs of the comic book reading community in the DFW area in the only manner one can expect from a locally gay-owned business – fabulously!

Since its last redesign, when Zeus won the Will Eisner Spirit of Comics Retailing Award in 2006, design trends evolved, and how we organize and display our code has matured. Zeus went through many attempts at integrating its point-of-sale system with an ecommerce solution. I’m embarrassed to admit, its first version, not having any experience in ecommerce (how hard could it be?) used FileMaker Pro and Lasso. Looking back, I’m stunned by some on my coding and design decisions. Some of which locked the site into arcane structures from which are not easily broken. And some still exist.

The old method for adding something to the site was simple—make a new folder and add some new tables and call it good. Want a forum? Install Aterr. Want a checklist? Add a new CodeIgniter folder. After all, what’s one more, right? After a while, we ended up with many little systems and no way to support them all.

The site’s design needed consistency from its previous version as well. Too dramatic a departure and it loses its branding. We weren’t looking for a fresh start, just a face lift (with enough skin for more adjusting later).

Our approach to ecommerce was simple: always be closing. One of the lessons learned from out previous cart solution was the more steps a customer has to take to complete an order, the more likely we’d lose the sale. When you go into a retail store to buy a comic, you don’t expect to be a member of that shop. When was the last time you walked up to a counter to pay for your goods to have the clerk ask for you username and password. I don’t have a user name. I just want to buy this book.

This was how our previous cart worked. And I’ll say this first, after trying out X-cart, Zen Cart, Squirrel Cart and later Magento Commerce, Shop Script was the only solution with the simplest way for us to control data from our point-of-sale source. After adding all the items to the cart, the user would have to create an account, add records to the address book for both shipping and billing, choose those records and add them to the order, and then they could finalize their purchase.

In the current system, we’ve taken out the need for membership. We don’t need it. We don’t really want it. We certainly don’t want to support it, if a customer forgets their password. Instead, customers get a tracking key upon return from Paypal. We don’t want your credit card info either.

In the next few weeks, I hope to have a downloadable version of the ecommerce solution, so stay tuned.

Is zeuscomics.com all done now? Hardly. Out of the gate, I’m already tracking new errors plus some old ones that will be address by the next release. Fortunately, one of the design/coding goals was to be able to change and grow the site as needed. Stay tuned for that too.

http://www.zeuscomics.com

Twitterific -> YouTube -> Fail

Just how long does it take for a YouTube video to become available on the YouTube iPhone app?

Seriously, if YouTube accepts .wmv, .avi, .mkv, .mov, .mpeg, .mp4, .flv, .ogg, 3gp and outputs to multiple .flv, mp4, 3gp… OMG, why then is the link I just tapped not available?

I understand that once uploaded, videos take time to convert for display. Having uploaded some from my own iMovie library, waiting for YouTube to do its magic without a progress bar is torture. But once it’s done and properly playing on the website, the video still has to become available for HD (if available), mobile, etc.

As we become more connected on more networks on new devices, our content experience should become more homogeneous. Websites should get closer to looking the same on our desktop computers as they do our mobile devices. Instead, because of mobile phones and netbooks (more specifically, their wireless connectivity) web designers, who once enjoyed building for higher display resolutions and bigger bandwidth, find themselves thrown back into building sites that are “dial-up” friendly. It’s a whole new browser war sans Netscape Navigator.

Which brings me back to YouTube on the iPhone. Video codec H.264, briefly put, is designed for both high-def and small bandwidth playback. Since YouTube offers multiple versions of the same video, it has to take the original video upload and convert it several times. And since the only way to view YouTube on Apple TV or the iPhone is with h.264, YouTube needs to make additional conversions/transcodings.

In the end, content for the web isn’t just for the browser. It includes phones, game consoles, dvr (TiVo), and any future devices we don’t yet know we need. And all of them need the same content in their own specific formats.

All of this means that the next time I see something along the lines of “@amboy00: too funny! http://tinyurl.com/pqhugm,” I’ll probably have to wait until I get back to my desk to see the funny.

Killer WebKit

As a follow up to yesterday’s woeful tale of using WebKit’s proprietary css properties, I wanted to follow up with a couple examples of how one can use these features without getting all “bevel-ly”

The only benefit of text-shadow is not downloading graphics for what can be expressed in css. The same goes for -webkit-border-image, -webkit-gradient, -moz-border-radius, anything that keeps a web designer from having to launch Photoshop is a boon to bandwidth.

Here are two examples of using some WebKit css gradients.*

Update: You must have the Chrome 2.0 or Safari 4.b for these to work.

Example 1. is brought to you by “Killer Queen”

This similar looking display to that of the iPhone album display uses a radial gradient (opposed to a linear) as the background for the track names. The overall effect is a dim light. The odd numbered tracks also use a gradient to take advantage of -webkit-gradient’s support of alpha values.

Example 2. is a css calendar.

This one combines linear gradients and javascript arrays. Because -webkit-gradient can use rbga formatting in place of the usual hexadecimal value, calculating the values from color to another was much easier.

The drawback to these browser specific properties are, well, browser specific. While adding a gradient value to your div id=wrapper might give it a groovy drop shadow effect on Safari, nothing is happening on either Firefox, and much less for IE.

The workaround at this point is to browser detect.

if(jQuery.browser.safari) {
$('#wrapper').addClass('problem-solved');
}
else {
	$('#wrapper').addClass('wah-wah-wah');
}

Or whatever.

Specimen 7

Someday, all the nifty Photoshop Blending options will be available as CSS properties. Mark my words! In the mean time, we’re kind of stuck with drop shadows, and now gradients (and text strokes) for WebKit browsers. Too bad you can’t use them together.

In order to take advantage of the background clipping, the color needs to be transparent. First off, that pretty much ruins any other browser from displaying text. So this is only useful to Safari users (not even the iPhone currently supports it). In Photoshop, you can get around having a transparent color and still having a drop shadow by setting that layers Fill Opacity to 0% while the layers opacity at 100%.

Also, using this technique has some odd behavior with padding. In my example, I couldn’t set padding to the parent div without the effect inheriting that padding. Restating the padding didn’t affect it either.

Here is the example: webkit-background-clip.html

Now, you can add the -webkit-text-stroke and that will work with text-shadow, but only on the stroke and not the text. I’ve yet to find an example that uses all three without looking like one of Superjail’s Doctor’s genetic experiments.

Perhaps it is for the best, getting these to work together might have been the next blink.

Twitshirts by Amboy00 (that’s me!)

For example, the popular ajax loader file that hails from Apple’s own asynchronous progress indicator, has 12 points and loops around once a second. Well, for one thing, 12fps is really choppy (so I’ve made the fading spokes a little more smoother at 24pfs), but it already plays slower on Apple’s nifty browser.

jQuery to the rescue

Did you know that jQuery can control css background positions? Are you thinking what I’m thinking?

But first, back to drawing board

So the first part was to break up the animated gif frames and spread them out across a very long canvas. Since Photoshop no longer opens animated gif files (unless you own ImageReady somewhere), Fireworks can open the file. Use Fireworks to export the frames to individual files and THEN Photoshop can import all the files as a stack.

File > Scripts > Load Files into Stack…

For our ajax loader, expand all the layers next to each other and then save it out to its own gif. The file size won’t be that difference in fact.

All of the frames set side by side

Now let’s get back to jQuery

In our html, just set the div with a width and height to match your gif to prevent clipping and let the script do the rest.

Now we have a script that will snap the position of the background over each “frame” at the correct frame rate. Actually, the frame rate is not divisible by 1000, but it’s close and it’s not like you could tell.

The only problem with this script is that it’s constantly running. If you look at the page in Firebug, your going to see the code whipping around with new values all the time. Annoying! Also, chances are your page isn’t going to need some animation playing constantly. Ajax loaders are intermittently called when a simple action is called as a… asynchronous progress indicator! Who knew.

So we’re going to put in a cancel command to this script: clearTimeout.

Add in a toggle so show how to turn on and off the animation and were done.

It even works on ie6!

Take a look! example