ContactProjects
This is a list of the current non-commercial projects I am working on.
Learning Ruby
My background is in mainframe systems, which typically involves writing in so-called "third-generation" languages, such as, COBOL and PL/1. Whenever I've had to build web front-ends to test out Web Services (for example) I've hacked together some HTML using Javascript to invoke the xmlhttp class. Looking at the various OO languages around, I liked the look of the Ruby syntax (over Java and the .net offerings) so bought the definitive book (co-written by the Ruby creator, "Matz") and am currently working my way through it.
Experiences so far have been interesting - the Ruby philosophy being that nothing works in an un-expected way, and that seems just about right. Everything is an object, even the basic classes like 'string' and 'integer' inherit from the object class. Also useful is that numbers are arbitrarily large ... swapping between INTEGER and BIGINT types as they require. I've heard it described as a simple scripting language, yet it seems more useful than that.
One of the issues with using a new (and still developing) language is that most of the peripheral artefacts are either in a state of flux, or have a variety of competing options. This seems to be the case with Ruby and graphics output. At the moment I am looking at GTK+ but this itself involves understanding Cairo graphics in many cases, and I'm considering that currently as opposed to GraphViz/DOT.
Stock Dealing
Using Ruby I am also investigating automated stock-dealing, hence my particular interest in graph drawing.
At present, I have most of the basic system in place, although some considerable code refactoring is required(!) I am getting more into GTK now, and am currently building a 'control centre' to show the system activity. This is based upon a single window, with multiple re-sizable panes inside it; each pane having a multi-tabbed capability. I will drop in a few screenshots once it has some proper content to display.
System Architecture
Myself, and a former work colleague, have started to put together our thoughts on what we consider to be the Principles of System Architecture. Between us we have over 40 years in IT ... principly designing and developing enterprise-class applications. We think we can lay down the foundations of what 'good' system architecture is (or we're at least willing to give it a try).
Using pbwiki to host thoughts so far (the site is closed to public access for now).
