We have now seen our storm cell editing application grow in complexity as we start adding even just a few features. The stormcell editor has a gamut of interactive features and can delete storm cells and save the edited stormcells. And for good measure, this application is cross-platform and can work using just about any of the major GUI toolkits that are available, all in approximately 200 lines of code. Now, before we start patting ourselves on the back, there is still a lot more to be done. The editor still does not display any storm tracks, which will be another set of artists to manage along with the storm cell polygons. The track and storm cell display will need to be maintained together as they share a common underlying data. For example, the selection of a track should also trigger a selection of a storm cell in that track, and vice versa. The deletion of a storm cell should also trigger an update of its track line.

Managing all of this in more traditional procedural coding...