Hi Guys,
@Allen, I've been meaning to push my implementation to SVN for you (but SF appears to be borked??) - my code is its own parser using your string utilities - if I had realized I was going to use a real .mpd file, I probably could have opened it as a file object and traversed it for parts...the code was born out of parsing a simple text list. Well, we can clean that up. :-)
@Roland, the only problem with using steps is that relation names are (currently) fundamental to the schema of the system. In other words, it's sort of important to know that a part is a shutter or a window pane.
I suppose a program that wants to ignore relation names could _read_ the file without the meta comments, but as long as the central schema is to have relation names, saving work compliant with that program (and risking not having the child name metas) would result in useless data.
In other words, my thought was that if we want to _require_ names, I should make a format that won't function at all without them.
@All: are relation names necessary? I think they are. For example, most two-wheel holders can take the same wheel hub part in two locations; the relation names are the only user-identifiable way of picking which one to use.
cheers
Ben
@Allen, I've been meaning to push my implementation to SVN for you (but SF appears to be borked??) - my code is its own parser using your string utilities - if I had realized I was going to use a real .mpd file, I probably could have opened it as a file object and traversed it for parts...the code was born out of parsing a simple text list. Well, we can clean that up. :-)
@Roland, the only problem with using steps is that relation names are (currently) fundamental to the schema of the system. In other words, it's sort of important to know that a part is a shutter or a window pane.
I suppose a program that wants to ignore relation names could _read_ the file without the meta comments, but as long as the central schema is to have relation names, saving work compliant with that program (and risking not having the child name metas) would result in useless data.
In other words, my thought was that if we want to _require_ names, I should make a format that won't function at all without them.
@All: are relation names necessary? I think they are. For example, most two-wheel holders can take the same wheel hub part in two locations; the relation names are the only user-identifiable way of picking which one to use.
cheers
Ben