Interesting, thanks a lot. cheers, Loïc
On Mon, Dec 7, 2009 at 6:50 AM, Thomas Paviot <tpav...@gmail.com> wrote: > Hi Loïc, > > The overview picture from the OCC website is a kind of functional > architecture diagram, which does not explain anything about implementation > details. > > OpenCASCADE is organized as a set of 6 functional sets: > - Application Framework, > - Data Exchange, > - Visualization, > - FoundationClasses, > - Modeling Algorithms, > - Modeling Data. > > Then each OCC python module is releated to one of this package. Marco > Nawjin contributed a very intersesting post on this ml in march 2008: > attached are 6 pictures that show the links between the python modules and > those 6 packages: > https://mail.gna.org/public/pythonocc-users/2009-03/msg00109.html (On > these images, each red box is a python module available in pythonOCC). > > Regards, > > Thomas > > 2009/12/6 Simon Loic <simon1l...@gmail.com> > > Thanks again thomas for your advices. I'm reading Roman's blog articles, >> and start having a clearer idea on shape definition (topology vs geometry). >> Feel free to add any other valuable documents. In particular, it would be >> interesting to have docuents (diagrams or whatever) explaining OCC modules >> relationships and why not integrate externals module like salomegeom/smesh. >> For instance I found this one http://www.opencascade.org/occ/overview/but I >> don't consider it very informative(as one have to guess relationship >> by oneself)... >> Anyway, I think I start to understand how things are organized : >> The core object is the TopoDS_Shape class, and then there are in on hand >> geometrical/topological algorithms to modify/create them and in the other >> hand viewers to visualize them. >> Is this right? I guess things are more complex than that. >> friendly, >> Loïc >> >> >> On Sun, Dec 6, 2009 at 3:17 PM, Thomas Paviot <tpav...@gmail.com> wrote: >> >>> >>> >>> 2009/12/6 John Griessen <j...@industromatic.com> >>> >>> Thomas Paviot wrote: >>>> the most important concept to start with (and to >>>> > understand) is the topological data model on which OCC is built. The >>>> > TopoDS_Shape class (and it's derivatives TopoDS_Edge, _Face, _Wire >>>> etc.) >>>> > is the big deal. Everything in OCC is based on this object (topology >>>> > building, geometry, data exchange etc.), >>>> > - as a consequence, the best introduction to the OCC kernel is the >>>> Roman >>>> > Lygin's blog: http://opencascade.blogspot.com/. I suggest you start >>>> with >>>> > the "Geometry and Topology in OpenCascade" >>>> > chapters: >>>> http://opencascade.blogspot.com/2009/02/topology-and-geometry-in-open-cascade.html >>>> > . Roman definitely knows OCC perfectly and is able to share his >>>> > knowledge in a very clear manner. >>>> >>>> Thanks, I'll read that. I'm new too. >>>> I'm interested in open hardware development and manufacturing niche >>>> market products and selling them. >>>> >>>> John Griessen >>>> Austin Texas >>>> >>>> >>> Hi John, >>> >>> Welcome to you. Feel free to share your first experiments with us and to >>> ask for any help. Questions from new users questions are often fundamentals >>> and give a very interesting feedback. >>> >>> Best, >>> >>> 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 >> >> > > _______________________________________________ > 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
