Thanks for the info.

So if i understand correctly this is only for user interaction / interactive
application development, and not really necessary for creating simple/static
geometry generator etc..? How about the other salome modules, the meshing
for example, does this require any use of the SGEOM module or is it
independent from that?
Basically what im trying to figure out is where i should start learning, and
what parts i can skip for now, or if there are modules that make other
modules obsolete...

Henrik


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

Reply via email to