Well I finally managed to figure out some of the problems I’ve been having and upgrade both MySQL and Drupal.

As you will notice, the site theme has changed as a result, and it’ll probably take me a while to get things straight.

The route that I took in the end was to use mysqldump to back up the entire database, upgrade to MySQL 5, and restore the database from the dump. This seemed to work fine and left me with a working database with my existing 4.7.0 install of Drupal.

I then upgraded Drupal in stages from 4.7.0 -> 4.7.6 -> 5.0 -> 5.1, running update.php at each stage. A bit laborious perhaps, but it worked without a hitch.

Thanks to D’Arcy Norman for a handy link, which put me on the right path.

I keep meaning to work on a new one, and was googling around today when I came across this.

I got sufficiently distracted to post a comment:

Link http://climbing-the-hill.blogspot.com/2007/06/on-severely-misguided-nature-of.html

I'm currently writing code for four platforms, using three IDEs (Eclipse, XCode and VisualStudio), and it's driving me bonkers!

I've said it before, but I'll say it again - why oh why doesn't Apple consider freezing XCode development and switching over to using Eclipse. I know that XCode has some nice features but generally I find it pretty clunky and I can't believe that all the good stuff couldn't be reimplemented as Eclipse plug ins.

Eclipse, on the other hand, is really solid but a little bit lumbering and confusing at times - I'm sure it would really benefit from some Apple user interface input.

So once that's happened (I wish), I just need to convince Whole Tomato software to reimplement Visual Assist for Eclipse, and then I'd be laughing...

Every now and then I come back to using XCode for some reason or other.

And every time that this happens, I am once again amazed at just how bad it is in many ways, at least for C++ development.

My current bug-bear is the code auto-completion - when you start typing the name of a function or variable and it tries to jump in there and suggest something for you.

On the whole, the suggestions that it makes seem to have got a bit better since the last time I used it, and it seems to manage to make a suggestion in a reasonable amount of time (maybe that's just because I've got a MacPro now).

The interface for making the choice, however, is awful. The thing that's really annoying me is that there appears to be no way of having it pop up suggestions, but allowing you manual control over whether to accept a suggestion.

It seems that you either have to manually pop up the suggestion box (which I don't want to do - I always want it to suggest things), or you can have the box come up automatically, but as soon as you hit any key other than escape, the currently selected suggestion will get inserted. This is truly awful user interface, since I'd put the success rate for it's suggestions at 50% at best. What this means in practice is that it is endelessly inserting the wrong text, as I type quickly and often the suggestion box has come up, an insertion has been made, and it has gone away again - before I've even registered that it was there.

I really hope that I'm just being stupid, and that there's actually an option to make it put up the suggestion box, but only insert the suggestion if I press a particular key (e.g. Return). This is the way that Visual Assist works, and it's a lot more intuitive (not to mention a lot safer).

It's been a while since I used XCode, so I was a bit baffled when debugging recently when I couldn't find a way to view a wchar_t* based string.

Surely there must be a way?

As it turns out, there isn't a way to do this that's built in to XCode (amazing!), but XCode can be extended with plugins, and Apple provide a sample plugin that does what I wanted.

To save everyone else going through the same length process that I've just gone through, here's how you do it:

You can get the sample project from http://developer.apple.com/samplecode/WcharDataFormatter/.

Build it with XCode (I built the debug version), and copy the resulting wchardataformatter.bundle into "/Library/Application\ Support/Apple/Developer Tools/CustomDataViews/".

One pitfall to look out for - it appears that the bundle has to be built for the native architecture that you're running on. By default, the project is set up to build for ppc, so if you're on Intel you'll need to change this to i386.

Once you've installed the plugin and restarted Xcode, you should find that when viewing any wchar_t or wchar_t* string, the Summary column in the debugger contains the correct character/text.