Interesting! The role of sgeom was blurry to me too. Still I don't get the name (GEOM) if its main focus is parametric modeling!! At least PAF name is much clearer ;-) So PAF is a pythonic extension of sgeom which is a simplified API of OCC topological naming. I've read lately some of the doc of OCC about Ocaf, and I must confess that I had hard time understanding ( still a lot fuzzy). Yet I had the felling that parametric modeling was using some Functional mechanism embedded in OCAF framework. However, OCAF is used for many other thing than parametric modeling, in particular keeping track of successive modifications. 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? Loïc
On Sun, Dec 13, 2009 at 12:28 PM, Thomas Paviot <tpav...@gmail.com> wrote: > 2009/12/12 Henrik Rudstrom <hrudst...@googlemail.com> > > Hi all, >> Been taking a few looks at the sgeom module, trying to find some >> documentation on its purpose, but there's little docs to be found. >> Looking at the methods/operations it seems to have some overlap with the >> rest of opencascade, and it also seems to be geared towards interactive >> application development ??? >> Could anyone perhaps shed some light on Salome geom, and especially its >> role within the python-occ? In what cases is it to be used? as an >> abstraction layer for the whole occ or just for specific >> functionalities/contexts? What is the relation between the OCC types vs >> SGEOM types? >> >> Thanks in advance >> >> Henrik Rudstrom >> >> > Hi Henrik, > > Our initial purpose, with Jelle, was to add parametric modeling features to > pythonOCC. OCC 6.3.0 provides a mechanism (topological naming) making it > possible. This is however quite hard to understand and implement. > > The Salomé project already offers a parametric modeling module, named GEOM, > that is based upon OCC 6.3.0 topological naming. This module was extracted > from Salomé and released as a standalone package by Fotis ( > http://sf.net/projects/salomegeometry). When we started to work on > parametric modeling with Jelle, we had three choices: > > - implement something completely new from scratch, > - port the C++ salomegeometry code to pythonOCC, > - wrap to python the C++ salomegeometry library. > > We decided to choose the third solution (the quickest way to have something > running, easier to maintain). The wrapper to SalomeGeometry is composed of > the following additional python modules: Archimede, SGEOM, GEOM_Algo, > GEOM_Impl, BlockFix, NMTDS, NMTools, Partition, ShHealOper, Sketecher. Each > of this python module is deeply integrated to pythonOCC (for instance, the > SGEOM modules depend on TDocStd, MMgt, TCollection, TFunction and Standard). > You can use all the OCC algorithms over a TopoDS_Shape generated with a > GEOM_algo object. > > To simplify the access to all the objects/methods, Jelle and I developped a > package named 'Parametric Application Framework' (PAF), that is intended to > abstract the salomegeometry internals, and make something more pythonic. The > PAF still need to be improved. > > Regards, > > Thomas > > > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users > >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
