I think karma maybe useful but not as useful as a -1 kick.

And if someone had a lot of good karma banked up would their kicks count more? That could be a good feature, but you would have to find an ideal multiplier so they "good" kickers do not overwhelm the rest of the kickers with only their links.

I noticed the "kick it" links look a bit different on my blog now.

http://brennan.offwhite.net/blog/2007/06/30/aspnet-ajax-with-static-javascript-source-files/

The blog requires an account to post a comment. Boo I say!

I agree. It is not a blog without a feed or comments.

I am not sure how I feel about the uppercase keywords. I do not like holding down shift all that often but it does make the scripts look more readable. It does make sense when a script is viewed outside of SMSS where it is not color-coded. But I use Notepad2 which does color-code known files like SQL scripts. But in a book that is in black and white I would prefer the uppercase keywords.

As for prefixing, I like to prefix common objects. The ASP.NET Membership provider creates a set of tables and stored procedures which are all prefixed with aspnet. I like that because I know they are a part of that system. For the applications I build I do the same so that a single database can stay organized with many groups of objects without a potential conflict. A set of schemas could also be used, but I think that over-complicates matters because that pulls in additional requirements for permissions. I try to only use schemas when I intend to limit access to a set of objects.

Interesting, but I really do not want to add scripting to CSS. The W3C worked very hard to cleanly separate structure, style and behavior into XHTML, CSS and Javascript in a way that allows them to work well with each other. You can already have Javascript instrument your XHTML and CSS. And with a library like jQuery you can do some amazing things with CSS selectors to adjust style and behavior. Instead of adjusting the CSS to add behavior I would instead emit dynamic Javascript with the settings it needs to alter the CSS as the page is being rendered. Also, I think combining multiple CSS fragments on the server is an excellent use of this CSS module. I always like to keep my CSS files organized but either you have to use one huge file or break it up into many files with many LINK references to them. It would be more efficient to place all of the CSS into a single file with a single LINK reference. And when pushing down this composite CSS file you could determine which fragments to include based on the browser at the other end. I personally would write all standard CSS with some small adjustments for browser specific fixes as needed. With the latest IE7 and FF such fixes are not as necessary as they were with IE6 which is going to be around a while longer.