I support the idea. However, if you want the part/primitive replacement to not be noticeable to the end user, then things become exponentially more difficult. For instance, when you use Tore Eriksson's LDBoxer program - which has multiple variants of each brick depending on whether their tops, bottoms, or both can't be seen by the user - you have to run the program each time you make changes to the model.
A 'dumb' system that doesn't take part visibility into account would be easier to implement, and is what I use in Datsville.
[edit]
I also keep this thread bookmarked in case something comes out of the discussion.
A 'dumb' system that doesn't take part visibility into account would be easier to implement, and is what I use in Datsville.
[edit]
I also keep this thread bookmarked in case something comes out of the discussion.