In researching a solution to give us reliable rolling upgrades it seemed helpful to have an overview of the current layout of the code.
It is incomplete (missing objectstore, only begins to deal with the public api side of things, no db interaction, somewhat haphazardly laid out), but I think it is a good basis for a visual language to describe this stuff. I looked at UML and call graph generation stuff prior to making it but nothing really captured the various metaphors we're working with. It's a graffle file (and an exported png) so tough to update without a mac, but I would be happy to hear people's thoughts. http://term.ie/data/nova.graffle http://term.ie/data/nova.png --andy
_______________________________________________ Mailing list: https://launchpad.net/~nova Post to : [email protected] Unsubscribe : https://launchpad.net/~nova More help : https://help.launchpad.net/ListHelp
