Guggenheim New York
The Guggenheim New York is likely the one museum in the world where crap hangs on art.
Comment?
Web 1.0++
Behind every great Web 2.0 application is a great Web 1.0 application. Just another way to explain progressive enhancement…
What I Learned at The Spring Experience: Lesson 2
Dirty Harry’s Match
“A man’s got to know his limitations.” — Clint Eastwood as Dirty Harry
“..and if he forgets, his wife will remind him.” — A married friend
.NYET
An open-source .NYET developer laments Microsoft is the open-source Nazi, “No open source for you!” Well, you’ll know the plight of the .NYET crowd has turned around when you hear them complaining, “get .Nhibernate out of my POC#O’s!”
Time-lapse Progressive Enhacement
A few weeks back a friend broadcast over email the image above, which, as another friend put it, depicts “the way to do it.” The “it” is modern web design, which was just the topic of an excellent “The Spring Experience” talk by Mike Stenhouse I attended today. The “way” is called “progressive enhancement”, which involves designing a web ui in progressive layers, beginning with semantics (xhtml), progressing to styling (CSS), and capping it with behavior (JavaScript).
Mike detailed the many advantages to this approach, but one stood out that I hadn’t considered before, using xhtml as the contract that establishes the division of labor between CSS designer and JSP/Java developer. Once the xhtml content is developed, the CSS designer constructs styles that render the content in a desired way, while, possibly concurrently, the Java developer programs a server-side module that generates the agreed-to xhtml.
(A fellow attendee mentioned a similar alternative: using xml as the contract, which the developer generates and designer transforms into xhtml using xsl.)
What I Learned at The Spring Experience: Lesson 1