Testing ToolBook HTML on Google Chrome
I have just downloaded the new open source browser by Google called Google Chrome, while a little skeptical about a giant search engine company like Google now also doing browsers (when will they stop? Google Cars? Google Beds:-)) I really do like the new browser: JavaScript seems lightning fast compared with the other browser current installed on my computer (IE7 and Firefox) and Chrome has some nice features (the omni bar/omni field being my favorite).
Anyway the point with this post is not to go through all the features of Google Chrome (Google does a good job at that here) but rather to let you know that I have tested the HTML output produced by both ToolBook 9 and Toolbook 9.5 (beta).
ToolBook 9
While the index.html file in ToolBook 9 HTML content gives a message that the browser is not supported - you can bypass that by pointing Google Chrome to the index.html in either the IE or the NS directories. And if you really needed the support you can do a manual edit of the JavaScript in the bootstrap.js file located in the webexport directory of ToolBook’s HTML.
ToolBook 9.5 (Beta)
It works out of the box!! If you point Google Chrome to the Index.html file in the webexport directory ToolBook HTML treats Google Chrome as if it is Safari and the contents of the safari directory is displayed. This is really cool.
Google says that Chrome is built on some components from Mozilla and Safari - which is what prompted me to test in the first place - but still it’s a nice surprise that it actually works in real life!!
Notes on the testing
I haven’t done any rigorous testing but verified that content looks OK and tested that that basic functionality like navigation and questions, scoring etc is working. I also tried the sample from my blog post called Controlling the Browser Window x to push it a bit (the sample use a lot of JavaScript to hack the ToolBook HTML Runtime) - and even that worked well.