Wevah has done it again and updated the nifty OS X utility Paparazzi!.

Paparazzi! is a small utility for taking full length screen grabs of web pages. The latest update adds support for saving captures as PDF, and added a paparazzi: url scheme to allow for launching from a browser via bookmarklet as well as some other changes and bug fixes.

First Impression: Nice idea but needs refinement. Flock, if you haven't bumped into the hype, is a new “social&8221; browser based on Mozilla.org technologies. Wraps up a bunch of so-called web 2.0 products (flickr, blogging, del.icio.us, feeds) along with your old fashioned view of the web into one user interface. Missing features aside, it just doesn't feel natural — yet. A few too many times I've either accidentally done something (bookmarking something when i wanted a context menu) or had to work too hard to do something I would have though would be seamless in the product. But those things I'll give some time and user feedback to get worked out. As for missing features, heres a few initial bugaboos: * No initial bookmark or other data import from Camino (my normal browser of choice). * With the del.icio.us syncing features it looks like some of the bookmarking features I'm used to in Camino or Firefox are missing — most disappointing is the apparent loss of bookmark keywords. * The bookmark integration seems like an all or nothing proposition. Maybe I'm an odd sort but I have many local bookmarks to machines that can't be accessed by an outside network, private bookmarks to admin interfaces here or there, bookmarklets, or other such things that I wouldn't want to share with the world. An extra &8220;publish&8221; layer here would be greatly appreciated. * A feature more of my choice in blogging tools then anything the Flock team could have done, but by using their interface to post I'm not getting access to any preview of my posts run through Textile. Sort of a pain for consistency — especially if I'm moving between the native web interface and the XML-RPC facilities. On a big positive, the core browser functionality seems as solid as I've seen Firefox be, and they haven't really broken anything on the way to adding the new tools. That's a real good place to be during these early preview stages and gives them plenty of room to focus on cleaning up the new tools going forward. EDIT FROM TEXTPATTERN: Well, I guess I need to work on the textpattern integration a bit. Kill the formatting from flock, run textile, and find a way to get category picking working.

Now that was a fun night of hockey that ended in Henrik Lundqvist’s first NHL shutout – not even OLN’s coverage could ruin it. Here’s a little roundup from the hockey blogs I’ve been following to help get you in the mood:

• Hockeybird: Can You Say Shutout?
• Puck Update: Goalie Kings (on former Ranger prospect LaBarabara)
• Toronto Star Blogs Hockey Page: Who needs practice?
• SportsFilter: Havlat goes five-hole
• Hockeyrodent: Just 893 To Go – Sawchuk’s Shutout Record In Jeopardy Too (ok now, the rookies are doing well, but lets not get too excited)

And as much as I’m hating the OLN personalities, and Clement getting the name of the wining goalie wrong TWICE after the game, I’ll probably be watching whatever they air tonight.

From Simplebits comes news that the first edition of Treehouse—a new PDF based mag on wed design—is up for free download.

Now, I know what you’re thinking—why do a web magazine as a PDF—but at 58 pages covering business to code it seems to be a nice start and the format seems to work.

I've mentioned my concern over existing hacks and reliance on them may be impacted by the pending release of IE7 before, but now the official IEBlog has posted Call to action: The demise of CSS hacks and broken pages.

Here is a list of common CSS hacks to look out for (please also consider their variations):

• html > body — http://css-discuss.incutio.com/?page=ChildHack
• * html — http://css-discuss.incutio.com/?page=StarHtmlHack
• head:first-child + body — http://centricle.com/ref/css/filters/tests/owen/
• head + body — http://www.dithered.com/css_filters/css_only/head_adjacent_sibling_body.html
• body > element — http://css-discuss.incutio.com/?page=ChildHack

We ask that you please update your pages to not use these CSS hacks. If you want to target IE or bypass IE, you can use conditional comments .

Sure, that's wonderful, and something that has been looming as a caveat to hack use since the first hack. But the post totally glosses over the reason many pages may now fail if they've used these hacks — that MS has fixed some, but not all of their CSS2 support. Just look at the example I used in that past post (happens to be the same one used in the first comment on this latest IEBlog post). If you fix the parsing of selectors, but don't fix the support for all of the rules that were being hidden then the page you're viewing is broken because IE7 is broken.