Vincent, to me, the GroupRelationData concept is not very clear. Can I have some questions?
1. Why not have just one table inside, and every engine that needs the data could create as much instances as necessary, one for every parameter? It would seem more logical than having that inside MetaBody. For instance, shared_ptr<GroupRelationData> SomeEngine::kn would hold kn's for various groups, kn->getParameter(g1,g2) would get the value. 2. Can you provide an example of how is it supposed to be used? 3. The micro-language for serialization doesn't feel like the right thing to do. Do you need help with the conversion in preProcessAttributes/postProcessAttribues? Of couse: It would be nice to have some shared material property class (such that I could say: all these spheres have material parameters #1, those have #2) -- shared_ptr's could be used for that; or we may add MetaBody::materials class that would hold those things. Right now, we have material defined separately in every body, along with things that differ from body to body (position, damage, ...). V. _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp