Monday, monday...

So wow, it's a miracle that even got to work this morning. Cassie sort of rolled me out of bed and onto the bus.

Anyways, a few things. One is that ChangeTracker needs to have a slight update: it will allow nodes of the structure it's tracking to be replaced by complex objects (arrays or objects) and then track changes to the whole structure (i.e. changing any child of the node you set as a complex object means the entire child-structure under that node is marked as changed). This is to allow tracking of arrays and lists in the only way that makes sense to me. It's not perfect, but until I think of something better, it will work (and it really should be good enough for the most common cases).

This morning I'm doing export configs - there's one for Commonwealth Audi/VW that I'm doing first, and then a more complicated one with Ride65 that will require either a perl hack or changes to the exporter. Changes to the exporter is more attractive. The problem is that ride65 maps values to ids, gives us a list of ids, and wants us to use those in our export instead of the values. If the mappings were small we'd just hack them right in there, but it's quite the hefty list, and that's not maintainable. So I'm thinking we can put a "mapping" section into input.xml (or somewhere) that's got a lookup table for values (drawn from a special table in cs3 db) and then make xslt queries on the table a-la "give me the id for make Volvo". I'm not sure how possible this will be to do, and I'll have to talk to Dave about it. Anyways, that's for later. Just wanted to get it down on paper. Er, whatever.