Hi Thomas. Thanks for trying making things clearer. Also I'm happy not to be the only one finding the naming conventions (if we can call it that way) confusing.
Hence, I wonder if it is easy and efficient to use PAF and OCAF in the same >> time. In that case, does OCAF handle, the modification made by PAF by >> default or do we have to implement extra features for that? >> > > I'm afraid I don't understand your question. What is your need? > Indeed, my question is not very clear. The thing is that I understood that OCAF provides some features for free. Quoting OCC team (from http://www.opencascade.org/occ/areas/cadcamproducts/) : "In addition to architecture OCAF gives you basic functions to implement Undo/Redo, Copy/Paste and Storage/Restore mechanisms that could be very time-saving." But, I understood, that those free features are not available for free for instance if you extend OCAF native attributes. And, as I have no idea how salomegeom and PAF are implemented, I wonder if Undo/Redo, Copy/Paste and Storage/Restore are still available if using PAF. Also, I'm wondering if there are conflicts between OCAF topological naming and PAF. But maybe it makes no sens using both of them (if they provide te same functionality)! I have to say that, things are not very clear in my mind (OCAF, PAF), therefore it's quite likely that my questions are totally crappy. In that case, don't waste your time trying understand them, I'll just have to get more comfortable with pythonOCC first and then we will see. Regards, Loïc
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
