Thursday Dec 21, 2006

Check Out This CSS Trick

This is an image of Phoebe taken from the Cassini spacecraft and subsequently improved by me in Photoshop by adding stars. Phoebe is a chunk of ice and rock that orbits Saturn, but the reason Phoebe is here today is to show us how completely rad CSS is. [Read More]

Friday Dec 15, 2006

Blog Redesign!

I've redesigned my weblog. I've always wanted to do it, but Roller's templating and theme system was too daunting. It's easy to tamper with the HTML your blog generates, but as a web designer by trade, I wanted total control over the HTML, CSS and JavaScript. Alas, lots of HTML-generation happens deep within Roller-specific Velocimacros that you have no obvious control over. So, if you really want control, you have to get intimate with Roller. You have to have its babies and cook it three square meals a day, and not complain when it doesn't want to cuddle. Gritting my teeth, that's what I finally did, and this is our love child.

Wednesday Feb 08, 2006

The Good, the Bad, the Ugly: Testing IE7's CSS2 Support

Now that IE has a public beta for version 7, and being the morbidly curious web developer that I am, I decided to take a peek and see what kind of hell I'll be living in for the next five years. The results? Instead of dying of stress-related heart failure in my late thirties, I'll be a worn out shell of a man hanging on well into my forties. W00T!

But seriously, while IE is improving, it still has a long way to go, as evidenced by this test suite of some glaring IE CSS deficiencies. (I'm not even going to attempt viewing the Acid 2 test in IE7 until I back up my hard drive.) Here are some of the hilights:

The Good: adjacent selectors, first child pseudo-classes, child selectors, attribute selectors and multiple class selectors work. Fixed positioning works, and fixed background attachment works properly. Box overflow works like it's supposed to, instead of the box expanding. The sound you hear is years collectively being added to the lives of web designers worldwide.

The Bad: No max/min-width/height support. No CSS table display support. Dang. With these two things, life as a web developer would almost be, dare I say, easy?

The Ugly: E7 still positions backgrounds from the outer border edge, not the padding edge. Still no support for border-spacing. There are still some box model inconsistencies.

So all in all, I raise my glass to the IE team, but I also say "keep working." I'm looking at you, IE 8.

Wednesday Jun 23, 2004


As an XHTML/CSS advocate amongst Java/XML nuts, sometimes the Web Standards sermon falls by the wayside. One of the reasons for this, perhaps, is that the typical Java/XML nut lives in a heady world of dreams.

When I refer to a Java/XML nut (JXnut, from now on), I mean this: There are web developers who find Java and XML useful, and there are JXnuts. JXnuts are web developers too, in a manner of speaking, but JXnuts tend to say things like "The web is dead" and "So long for the web browser". JXnuts loathe the web and want it to go away. They want it to be replaced by something grander.

I say this because of history. During the late nineties JXnuts saw the convoluted, pulsating mass that the web had become, and they reeled. Being technical purists they sought for something cleaner and more expressive. JXnuts ascended into the well-structured world of Java and XML and, embracing it, never looked back.

If they had looked back, they would have seen that great sprawling mass shudder from end to end and begin to writhe like a vast, salted slug. XHTML and CSS reform had begun to sweep through the rank and file of web development.

I say all of this (in slightly exaggerated terms, perhaps) to hilight a subtle technical rift that exists among web application architects. At one extreme you have those who, in their own minds, deprecated HTML and its cohorts in disgust long ago and turned their focus to server-side solutions or alternative web architectures. At the other extreme you have those who, for various reasons, never got the memo that HTML and browsers were out of style, and went on to embrace XHTML and CSS as a powerful component of modern day web applications.

Personally, I find this disturbing. I'm one of the latter, of course. The rift creates a lack of synergy between two forces that otherwise would form a powerful alliance. I've seen great development efforts afflicted by old school client side coding techniques because HTML and browsers are, annoyingly, still the defacto standard for web architecture and, inexplicably, never vanished from the face of the earth. I've also seen a trend where those who espouse the virtues of XHTML and CSS get relegated to the status of gibbering pratt. They still get to "do their thing" if it doesn't sufficiently annoy any lead architects with circa-1997 HTML sensibilities, but their methodology is slow to seep into the strata that form the bedrock of modern day web architecture, because that bedrock is largely built and controlled by JXnuts (or their counterparts in .NET/PHP/whatever land).

If I could make any suggestions to help rectify the situation, I'd tell the JXnut to swallow his/her pride and try to understand the value of abstracting logical and graphical presentation using nothing but XHTML and CSS, and how this can result in a better, more modular web application. I'd also tell the XHTML/CSS nut (the XCnut, myself being a prime candidate) to try to understand the bigger picture of web architecture, and embrace some of the possibilities that fall outside the comfortable world of HTML and browsers.


My name is Greg Reimer and I'm a web technologist for the Sun.COM web design team.


« August 2016