I’ve written a new version of my LibraryLookup script for the San Francisco Public Library that works with Google’s Chrome browser. If you’re running Chrome, you can try it out by clicking this link. It should work regardless of your OS platform — in fact, it even works on Chromebooks! Note that this version of the script is a substantial rewrite from the Firefox version, so I’ll be especially interested to hear any bug reports. It works pretty well for me so far, but I still don’t use Chrome as my main browser.
Also, note that because LibraryLookup uses cross-site scripting, it has to run as a Background Page in Chrome, because of the way the browser was designed. That means it’s consuming some small amount of memory all the time, even when you’re not browsing Amazon. The amount of resources used should be negligible, but you should be aware of this before you install it. Enjoy!
One of Google’s many big ideas is Chrome OS, an operating system that essentially is a Web browser — nothing less, but nothing more. A Chrome OS computer, called a Chromebook, can’t install any software and it has very limited processing power and onboard storage. All the applications you use on a Chromebook are running “in the cloud,” which is to say they’re Web apps. Acer and Samsung are now shipping Chromebooks, and I recently spent some time working with Samsung’s latest model to see whether it has a place within my normal computing workday. The results weren’t particularly encouraging, unfortunately, though I think a Chromebook can be useful as a secondary way to access the Web around the home or office. Click through to InfoWorld.com to read my full run-down of the Samsung Chromebook Series 5 and how it stacked up in my tests.
For the truly geeky among you: In the latest post to my Fatal Exception blog over at InfoWorld, I’m taking a look under the hood of Chrome, Google’s new Web browser. A lot of articles make mention of how Chrome is open source. I actually put it to the test, by building a custom copy of it myself.
Along the way I found out a lot of interesting information about Chrome’s internals and how Google built it. On the plus side, it’s very clean, well-organized code. On the minus side, it looks like it’s going to be Windows-only for a good while, yet.
Anyway, I had a lot of fun doing this piece (it’s been a long time since I had a legitimate excuse to pull out a compiler on Windows), so if you have the hobbyist spirit, drop on over and join the discussion.