Development on Angus Thinks

SQLEditor 1.4b2

Fri, 17 Aug 2007 00:00:00 +0000

Another day, another beta. (Kind of)

SQLEditor 1.4b2 is now available, which is pretty much bug fixing against 1.4b1.

There were several issues with 1.4b1 including an annoying bug that would sometimes delete foreign key connectors when you deleted an unrelated table.

There are some fixes for other bugs which turned up and some improvements to undo/redo, to make it more stable when you undo or redo lots of things, one after the other.

What have I been doing recently?

Mon, 11 Jun 2007 00:00:00 +0000

Well no updates for a bit. Humm?

The main things I’ve been working on:

SQLEditor . Lots of things are being worked on. The user interface is being rewritten to improve speed and increase flexibility, the data layer is being rewritten to switch it to cocoa (instead of java), the JDBC code is being rewritten to make it use JNI instead of cocoa/java and a new crash reporting system based on Google BreakPad is being worked on. There are also some other things too like live source view and assorted bug fixes. 2) HTMLValidator . Also undergoing development. It recently moved across to use Sparkle (yey!) instead of the SQLEditor derived update system (which will also be replaced eventually). The final 1.0 release is due very soon now and several people have set in nice comments. 3) A new idea (still secret) :-)

Writing Unit tests for Cocoa

Wed, 15 Nov 2006 00:00:00 +0000

I realized something interesting today.

I use unit testing to (hopefully) improve the quality of my code.

With Java I use JUnit . With native Mac stuff I use OCUnit .

One really clever thing about OCUnit that I realized today is that if you have several SenTestCase subclasses, each with multiple tests in it, you can put all of them into one XCode target and OCUnit will automatically run them as suites in one test run. This means that you get a summary of all of the tests at the end.

static link library to replace dylib in mac os x

Thu, 26 Oct 2006 00:00:00 +0000

This post on the xcode-users list explains a neat trick on how to get xcode to link a static library instead of a dynamic library.

Imagine the circumstance: you want to use a particular non-standard version of a native library which is already part of the system; perhaps you want to use an old version with better compatibility, or a newer version with more features. The obvious thing to do is to take a static build of the library and add it your xcode project.