I found out today that Mozilla doesn’t serve up the latest version of “experimental” addons automatically to Firefox users. And until I can get them to get around to approving my addon, mine remains marked “experimental”. So you have to grab updates from the official download page. Get the latest news on the homepage.
I’ve always been extremely irritated by the simplicity of google’s search results. They require a lot more manual work to navigate than I can tolerate, browsing forward and backward, spawning a new tab to save interesting result, clicking between tabs, etc. Way too much clicking and jumping and tabbing and loss of context!
My lack of tolerance fuels my attempts to engineer workarounds. There’s no way you can live without google’s results any more, so the workarounds have centered on re-engineering the results page. The old perl scraper that I’ve used for the past 4-5 years has required an update every six months or so, but I’ve kept with it until the recent past (it no longer works). This weekend, I hammered out a better way (please insert trumpet blare):
The Google Results Walker Firefox addonI’ve posted it to the Mozilla Addons site (aka AMO), and I’m learning the hoops through which you have to jump to get “published” there. Looks like I’ll need lots of good reviews. If you want to help me out, sign in to the Mozilla addons site and post a review at the public page. NOTE that you have to actually provide a relevant full-sentence comment with the review, or, according to the Addon Reviewing Guide, it will just be deleted! Geesh!
There is a huge backlog of requests for new addons to be published. In the end, I may have to sign up to be an addon editor to get the job done. :>
It’s still a little rough and there’s a lot more I want to do with it. Check the wiki page for the current todo list.
What a horrible trial-and-error life web designers lead! After too much hair-pulling, this site now looks as it should on IE7. Issues:
- IE7 does not like div tags between li tags – so I reworked everything to oblige
- IE7 requires some hacking with padding and margin to get my rounded corners css to work
I hope I never have to touch it again (but I will).
This site now has pretty valid CSS and XHTML, and resizes pretty well too. Try it out with Ctrl+ to increase text size, Ctrl- to decrease. Change the resolution. Stretch it, pull it, bend it – better than Stretch Armstrong! (sorry, no green goo though…)
Added the following plugins to this blog:
They seem to play well together. I’m using the first for comments and the second for registration. They both use reCAPTCHA, which I think I like. 😛 Took a few theme/style tweaks. I guess I’ll be stuck with this theme for a while. :>
I’ll repeat this as often as I get the chance:
- The mouse is for CONSUMERS.
- The keyboard is for PRODUCERS.
- The only exception is for ARTISTS, who should be using TABLETS anyway.
Get your hand off that mouse! 😛
Here’s how to stay mouse-free using Clearcase version control in Visual Studio. To get to the place where you can set up your own “tools” to fire off via the keyboard, for VS2008, use Tools->External Tools, and if you’re still chugging happily along with VC6, use Tools->Customize->Tools.
| Purpose | Command | Version | Arguments | Initial dir |
|---|---|---|---|---|
| Compare with previous version | #ccpath#\bin\cleardlg.exe | VS 2008 FP1 | /diffpred “$(ItemPath)” | $(ItemDir) |
| VS 6.0 SP6 | /diffpred “$(FilePath)” | $(FileDir) | ||
| Show the version tree | #ccpath#\bin\clearvtree.exe | VS 2008 FP1 | “$(ItemPath)” | $(ItemDir) |
| VS 6.0 SP6 | “$(FilePath)” | $(FileDir) | ||
| Show checkouts (from 2 levels up) | #ccpath#\bin\clearfindco.exe | VS 2008 FP1 | “$(SolutionDir)\..\..\” | |
| VS 6.0 SP6 | “$(WkspDir)\..\..\” | |||
| Update view (from 2 levels up) | #ccpath#\bin\clearviewupdate.exe | VS 2008 FP1 | “$(SolutionDir)\..\..\” | #ccpath#\bin |
| VS 6.0 SP6 | “$(WkspDir)\..\..\” | #ccpath#\bin |
Then add keyboard shortcuts for the tools, and you’ll be that much farther from reaching for the mouse.
