Pope John Paul II George Carlin embraced the harsh realities of suffering head-on, and showed that they are an integral and unavoidable part of our pilgrimage here on earth, not to be feared but to be accepted willingly and even joyfully as the inevitable conditions for entrance into eternal life dumb.

Having just downloaded and installed MonoDevelop for OS X I can say that the process of getting up and running is an absolute breeze - only involving the normal mac ‘download, unpack and drop into Applications’ routine.

MonoDevelop (and indeed Mono itself) allows you to build several types of application - C++, C#, ASP.Net and the like. You can build cross-platform executables - either console-based or with a GUI (the application comes with quick-start project templates for the Gnome# and GTK# tookits) - and also web-based projects. MonoDevelop comes with the xsp server built-in so the code-compile-debug cycle is only a single click away (as a bonus it even opens your browser for you).

MonoDevelop is a Gnome application, so a minor annoyance when using it with OS X is the key-binding setup which requires you to use Ctrl over the Apple key for things like copy, paste and save.

I’m hoping to do some work on a mono-driven ASP.Net application, so I may be posting more on that in the future. For now though - I’d like to give a big thanks (and say congratulations) to the MonoDevelop team.

I just discovered by accident that right- (or ctrl-) clicking the time machine’s drive in Finder (but weirdly not on the desktop) brings up an extra ‘Backup Now’ option in the context menu.

• Dojo: The Definitive Guide
• Mastering Dojo
• Dojo: Using the Dojo JavaScript Library to Build AJAX Applications

All three books cover the core dojo library and dijit gui controls and also associated tools like the build system.

Dojo: The Definitive Guide

If I ever want to get a book on a subject and there is an O’Reilly Definitive Guide, I will choose that one - mostly based on having the Javascript and Actionscript equivalents. I have to say though that I felt a bit let down with this version, as DTDG isn’t as comprehensive as I’m used to from the series. While the coverage is broad (more so than the other books in this review), it isn’t all that deep in some key areas - missing out on some of the gotcha’s that I have found indispensable when working with Dojo.

I should make it clear that book is very clearly written with clean and helpful examples. It is also written with the clear intention of readers people build solid web applications beyond using Dojo.

DTDG does go into excellent detail about the Dojo environment - bootstrapping, the build system, the dijit life-cycle, browser utilities, OOP with Dojo, Event management and the Publish / Subscribe mechanism, Ajax / JSON / JSONP / JSON-RPC, and more besides. I think few people who aren’t Dojo committers could read and grok the book without gaining considerable insight.

This puts the book in context - it isn’t really for the average developer who wants to get an application up-and-running with Dojo. I would say it is for someone who wants a deeper understanding of the structure of the library, rather than how to hack something together with it. A good example is the explanation of dojo.byId(), a clear detailing of the vagaries of document.getElementById() - and why the former is more useful (however I’ll leave you to go and buy the book to find out the specifics ;).

Mastering Dojo

I would recommend this book without hesitation. I found it informative, helpful and really on-point while trying to create a fairly heavy application on top of Dojo. Written in the usual Pragmatic Programmer style, it is as easy to read through a chapter as it is to dig into for a specific answer.

Perhaps one omission is the DOH (which the book incorrectly refers to as the Dojo Object Handler) - perhaps correctly citing the fact that it is out of it’s own scope. Given that DOH is dojo agnostic (your project does need to use Dojo to be tested with DOH) I suppose that is fair enough, but I would love to have seen even an introductory chapter on it.

Mastering Dojo is structured in a slightly confusing way - confusing at least if you are used to The Book Of Dojo and it’s well worth searching for terms in the index (unless you’re reading a PDF!) when the chapter titles don’t look as though they contain what you need.

Dojo: Using the Dojo JavaScript Library to Build AJAX Applications

I’m afraid to say that I wasn’t especially enamored of this book - from its tongue-tangling and strangely-chosen title onwards. I felt that it missed a considerable amount about the basics of dojo - which is understandable given its title - without really giving enough detail or insight into building an RIA - which is not.

Using Dojo (the best shortening I can come up with) does give a reasonable introduction to dojo, and covers some of the fundamental forms of usage, but it really isn’t comparable to either of the previously covered titles.

Update 2008-07-03 : Alex Russell, one of the core dojo committers has also reviewed these books.

There were several parts to the problem:

• Iframe Transparency in IE
• Targeting the containing div node, the editor’s iframe tag, and that iframe’s body node
• Ignoring the weird default content that Dojo, or possibly the browser itself, adds to the Editor (a <br /> tag, but with a special attribute in Mozilla browsers)
• Removing the class once the user makes a change to the content

Ignoring all the rest, and a lot of the specifics (since I’m sure there are better ways to achieve all this) I’m just going to note how to get use dojo.connect to respond to a ‘click’ inside the editor area. It’s worth noting that using the normal method’s you would expect sort of work - but only when you click on the Editor’s toolbar rather than the inside the editable area. That being said, here you go:


<textarea dojoType="dijit.Editor" id="dijitEditor">Click Me</textarea>
<script>
dojo.addOnLoad(function() {
 var dijitEditor = dijit.byId('dijitEditor');
 var eBody = dijitEditor.iframe.contentDocument.body;
 dojo.connect(eBody,'click',onEditorClick);
});
function onEditorClick() {
 alert('you clicked the editor window');
}
</script>


NB - Not IE-friendly. This won’t work in IE because of the contentDocument property, which it doesn’t support - but you could use the document.frames[] array instead. Note that the iframe’s id is widgetid+’_iframe’ in all except Mozilla. So something like this:


dojo.addOnLoad(function() {
 var dijitEditor = dijit.byId('dijitEditor');
 var eBody;
 if ( dojo.isIE ) {
  eBody = document.frames['dijitEditor_iframe'].body;
 } else {
  eBody = dijitEditor.iframe.contentDocument.body;
 }
 dojo.connect(eBody,’click’,onEditorClick);
});


I really went down the rabbit hole for while chasing ‘ondijitclick’ and the ‘events’ / ‘captureEvents’ properties of the Dijit.Editor, but ended up using this fairly straightforward custom method.

I accidentally discovered a method for dropping the bluetooth connection properly, and removing the cycling message from the OS X menu bar:

1. Get iStat Pro’s free dashboard widget
2. Make sure your network connections are displayed when you start Dashboard
3. Wait until your connecting goes crazy, and won’t drop the connection
5. Fire up dashboard and, in the bluetooth pane on the iStat Pro widget, click the ‘Disconnect’ button twice

Cool.

Now if only that would help in reconnecting ….

<iframe src="iframe_source.html" id="iframe_id" allowtransparency="true" />

However, if you want to set the transparency with Javascript via the DOM, you must camelCase the property:

document.getElementById('iframe_id').allowTransparency = true;

Note - you must also make sure that <body> tag in the document contained by the iframe is also transparent in order for the parent’s colours to show through.

I had tried running Firefox 2 and 3 in parallel on my macbook, but found that 3 would always try and become the default browser, which annoyed me enough to get rid of it. Now though I’ve gone the whole hog and, while I do have FF 2 hanging around, I’m using 3 full time. The upshot is that I’ve been poking around at what extensions are available for average everyday webmonkey (btw - did you see that webmonkey is back?) and have been updated to work with FF 3 RC 1. Here’s my current list of installed extensions.

Update: 7th May 2008: these all work for Firefox 3 RC 2

AdBlock Plus

A pre-requisite for surfing the public web. Ads are so 20th century!

ColorZilla

Advanced Eye Dropper, Colour Picker and more. Brilliant stuff.

Delicious Bookmarks

Plugs your browser nicely into your delicious account.

Firebug 1.2 Beta

Indispensable. Nuff said.

Googlebar Lite

Ahhh, so much nicer than the big G’s own attempt.

Scrapbook

Sort of like your bookmarks, but actually saves the pages down to your hard drive for offline viewing. You can edit-before-capture and even spider whole sites (or sections thereof). Really quite nice.

TamperData

TamperData is to HTTP what Firebug is to the DOM.

Web Developer Toolbar

An oldie but a VERY goodie! Manage CSS, find stuff and another hot tip - until MeasureIt is updated for FF 3, it also has it’s own ruler system (in the Miscellaneous menu).

To the rescue comes Double Command, a Preference Pane add-in that will give you quite a number of options, including the somewhat obvious to my mind “Shift + Backspace acts as delete.”

It has quite a nice way of allowing a System setup, a User setup and a Current setup, and a pretty hefty number of altered key options, however I was happy to just stick to the one change (I’m a big fan of the extra “Enter” key next to the arrow keys, and somewhat miffed that it might disappear).

#!/bin/sh
curdir=`pwd`
if [ $# -eq 1 ]
then
usrdir=”$1″
ls | xargs -I % echo `pwd`/% | sed -e s!$usrdir!!
else
ls | xargs -I % echo `pwd`/%
fi

You can optionally provide an initial part of the path to ignore. I use this when writing code change emails where I have to list the updated files within a codebase (and I’ve touched most files in a given directory) and I clip the local path up to the root of the codeset. Assuming the script is saved as “lspath”:

lspath /Users/pete/Sites/project/trunk

Even handier is piping it into the OS X clipboard for easy pasting:

lspath /Users/pete/Sites/project/trunk | pbcopy