...more recent posts
Xargs tutorial I need to look at some day.
(I make no claims that this blog is interesting to anyone else, as this post and almost all others show!)
The Golden Grid is another CSS framework (like the popular Blueprint and 960 grid.) I've yet to use one of these for anything, but I keep watching with hope. At this point my intuition is that these projects can save you a lot of time and headache, until you need to do something that a particular framework can't handle. And there's always some demand that breaks the grid. But I guess that's why I have a job so I shouldn't complain. Still, if I ever have time to update one of my personal project pages (like this one from the dark ages of the web) maybe I'll play around with one of these.
Some insane people have developed a text editor that runs in the browser. It uses javascript to draw everything into a canvas tag.
Bespin builds on this API to recreate a text editor from scratch. That’s right; rather than use the native facilities of every modern operating system that give you word processing features for free, Bespin rolls them from scratch, including such basic constructs as a blinking cursor and text selection.I mean, seriously, that's insane. But if they could make it work well it would be really cool. It's a text editor, but the goal is to focus on code editing and to deliver not just a usable product, but something you might choose over your current desktop code editor. It's like javascript's coming of age party in the sense that programmers are somehow magically drawn to writing code editors in whatever their language of choice is - but no one has had that urge until now with javascript.
Runs in FireFox as well as WebKit and Chrome nightlies. Project home page.
Falai website launches. Sometimes you disagree with a client about something (like having a front page with no information on it,) but you have to do it anyway. Still, all together, I think it's a pretty nice site. Little bits of jquery made some slightly tricky stuff very easy to do.
(Just started resolving for me, so it's possible you might see the old "site under construction" version of the site still.)
Eric Meyer on the deficiencies of CSS for layout. I've linked to a bunch of similar posts from others, and again I couldn't agree more. I'm linking again here because Meyer is the man; he explains the issue very well; and it's kind of funny how frustrated he is (in a "thank god someone else is this frustrated too" sort of way.)
Very good presentation (audio with slides): An Intensive Exploration Of jQuery. Assuming you know a little something about javascript and the DOM this is a great place to start.
Wow. Very cool. Google introduces canonical URLs. This solves the problem of losing google juice due to identical (or largely identical) pages being accessible through different URLs. You decide which URL is canonnical, and then put a special <link> tag on the other pages pointing to the cannonical URL. Now google knows to return the cannonical page in search results rather than any of the similar ones, and all your google juice flows to that one page.
The big example would be http://www.example.com and http://example.com. If your site is reachable at both addresses, and both are linked to from external sites, then your rank in google until now has been split between the two (this is simplified a bit, but still.) Now you can decide that you want http://example.com to be the "main" (or canonical) URL, so you just put a <link rel="canonical" href="http://example.com/"> tag in the <head> section of the www.example.com page.
But this is useful in tons of other situations since we're slicing our data up so much these days. Take blogs for instance. A certain post might be accessible from the front page of a blog, from a permalink, from a comment page, from a trackback page, from a search page, from a tag or category page, etc. In the past all of these different views of the "same thing" would be seen as separate by google; now you can pick one view to be canonical. This just really makes sense to me. Thanks google.
Cool, slightly depressing, and thoroughly comprehensive tables highlighting the readiness of major browsers to correctly handle advanced web techniques from PNG alpha transparency to all the fancy CSS3 stuff. That must have been a ton of work to put together. Just glancing at the page is a pretty damming indictment of Internet Explorer.
Check out the final table for the grand scorecard for each browser. Note that Chrome has an advantage in the "Past" category since it's a brand new browser with no past. Otherwise Safari has a slight lead over Firefox and Chrome although they all do pretty well. Opera does okay and IE sucks.
Cross browser javascript vector graphics library:
Raphaël is a small JavaScript library that should simplify your work with vector graphics on the web. If you want to create your own specific chart or image crop and rotate widget, for example, you can achieve it simply and easily with this library.I like the js syntax - pretty intuitive:
Raphaël uses the SVG W3C Recommendation and VML (mostly equivalent Internet Explorer implementation) as a base for creatinggraphics. This means every graphical object you create is also a DOM object, so you can attach JavaScript event handlers or modify them later. Raphaël’s goal is to provide an adapter that will make drawing vectorart (similar to Flash) compatible cross-browser and easy.
Raphaël currently supports Firefox 3.0+, Safari 3.0+, Opera 9.5+ and Internet Explorer 6.0+.
// Creates canvas 320 × 200 at 10, 50Check the demos, they're pretty nice looking.
var paper = Raphael(10, 50, 320, 200);
// Creates circle at x = 50, y = 40, with radius 10
var circle = paper.circle(50, 40, 10);
// Sets the fill attribute of the circle to red (#f00)
circle.attr("fill", "#f00");
// Sets the stroke attribute of the circle to white (#fff)
circle.attr("stroke", "#fff");