Hi Dirk, "Dirk Reiners" <[email protected]> schrieb im Newsbeitrag news:[email protected]... > > Given that the GOs use a factory my approach would be to derive from the > GO that > you need, handle the new classes in the derived one and let the base one > handle > the standard classes. I'm not totally sure if that works for all GOs, we > might > have to rearrange things a little to simplify that, but that was the idea. > Once > you have that you can override the GO factory so that your new GO is used > instead of the old one. > I also think that the derived classes can (should) handle all the specific details of the particular classes. However, some of the GraphOp already do account for the well established core classes (e.g. MergeGraphOp). My impression is that these base classes need a minimal awarness of the new group cores. E.g. the MergeGraphOp::isGroup is imho such a case.
Best, Johannes ------------------------------------------------------------------------------ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
