Sire

I've filled in the WorkSpace class and am sorting out how inter-process communication
will work. I have decided to create the skeleton of the messaging scheme, so that
this can be extended in Acquire.

Code is broken

I've fixed a bug in StringList (incorrect comparison function) and have added in the missing
code in WorkPacket.

Code compiles and works, with sirentest reporting everything is ok :-)

I've continued to work on the WorkPacket class. It is filled in, and I am now in the
process of cleaning up the testing infrastructure so that writing unit tests is
as painless as possible (if it is ever painless...)

Code is broken and I am off to lunch

I'm now working on the Siren threading classes, and have decided to move WorkPacket
into Siren from Acquire. This is because I am going to unite the intra-process
threading model with the inter-process Acquire model, and use WorkPacket as a way
of parallelising the code at all levels

Code is broken

I've sorted out the unit testing infrastructure and reporting code. It is now easy to
write class-level unit tests and get a full report of those tests. The report is held
as a TestReport object, which can be queried, and also streamed / saved, thus simplifying
the process of writing the infrastructure that will support the automatic running and
reporting of these tests.

Code is working :-)

I've been working on filling in the TestReport classes so that I can run unit tests
and get the results ;-). In doing this, I've ported over the toString functions
from Sire/Siren to this standalone Siren

Code is broken

I've got the code compiling and working, with the sirentest executable now available to run
automatic unit tests of all of the classes :-)

I've fixed bugs in the registration of classes (including a weird bug in which the
QAtomicPointer that held the class registry was reset to zero between static initialisation
and running the main function - weird! I worked around it by removing the thread-safe
code used for static initialisation).

Code is finally working :-)

I've added the editor classes and defined how the Interface system will work. I've filled
in missing functionality and now everything compiles and links. The next step is to
add the "sirentest" executable so that I can start testing and debugging the code.

Code compiles and links, but is unlikely to work

I've made more progress with the design of the mutable classes and interfaces.

Code is broken

I'm sorting out the way of declaring interfaces to classes, and have added in String and
StringList caches of the class names and interfaces to ensure speedy lookup

Code is broken

I've added some time and date classes, and the backtrace code, so that I can have
fully detailed and featured exception classes. Most of the code now compiles and
links - it is very nearly there :-)

Code is broken

I've filled in all of StringList and the exception classes and am now looking towards
the threading classes.

Code does not compile. Code is broken

I've filled in Siren::ByteArray and have sorted out the type-safe copying and
comparison functions (so that object_a == object_b will always perform consistently,
even if object_a inherits from object_b, e.g.
(object_a == object_b) == (object_b == object_a) for all cases.

Code compiles but there are link errors from missing functions

I've finished implementing all of the functions of Siren::String. This now provides
a unicode, translatable string class, which follows the Siren::Object rules
(const object), and which ensures that the program only stores one copy
of each unique string, thus minimising memory usage / improving string
comparison times, and reducing the size of streamed data files.

Siren::String compiles without error, but the rest of the code is broken :-(

I've made progress filling in the functions of Siren::String. I have decided to
use atomic reference counting to ensure that only one copy of a string is held
in memory at any one time. This will make creating and deleting strings a little
slow, but will speed up string comparison, and significantly reduce memory
usage for cases where strings are repeated (e.g. names of atoms)

I've filled in sufficient code for everything to compile, although a lot of functions
are missing, and a lot remains to be written.

Code is broken - link errors because of missing functions

Sorting out the "detail" directory....

Code is broken

Finally got internet installed at home, so can commit the last weeks code. I have been working
through Siren and copying across / rewriting the code necessary to make Siren into a
standalone library. I've added in a "Number" class, which represents generic numbers,
and a "String" class, which is a wrapper around QString, to represent generic strings.

Code is broken

Making good progress porting across the Sire/Siren classes into Siren. I've simplified
and consolidated the design considerably, and now have Siren::Object as the global
base class, and Siren::Obj as the general, weakly-typed reference class. I've
deliberately designed Siren so that novice and inexperienced C++ developers should
find it easy to understand and create Siren classes, and the burden of adding in
boilerplate code has been removed to a couple of macros that are easy to include.

Code does not compile or work, but it is getting there :-)

Committing the initial source code developed during the software project. Siren
has been extracted from Sire and the dependencies on third party code (e.g. Qt4)
are being reduced / removed. I am also taking the opportunity on simplifying
the design of Siren, and of implementing the type metadata system using
macros rather than complicated template functions (much simpler and more
light-weight).

Code does not compile, link or work, this being a first commit and all... ;-)