Hey everyone: Finally got around to getting my svn key set up, and... i think i've successfully committed Slicer to the tools directory in SVN. Can you guys check and make sure that (a) it is there, and (b) it works with the trunk version? I ran it locally before commiting, but i would like to make sure it works with the latest SVN version-- if It does not I will fix it. To test, please run ( from Tools\Slicer directory ): >python OccSliceLib.py parts\Test.STEP You should see a nice weird shape, a bunch of slices, and then a Test_Sliced.svg file produced.. I'm really looking forward to seeing this in a single- downloadable release-- i cannot wait to report this to the Reprappers, that one download gets them running! Thanks for all your help guys! Dave
_____ From: pythonocc-users-boun...@gna.org [mailto:pythonocc-users-boun...@gna.org] On Behalf Of Thomas Paviot Sent: Friday, June 05, 2009 10:09 AM To: pythonOCC users mailing list. Subject: Re: [Pythonocc-users] Assembly representation 2009/6/5 Bryan Bishop <kanz...@gmail.com> On Fri, Jun 5, 2009 at 8:52 AM, Thomas Paviot <tpav...@gmail.com> wrote: > 2009/6/5 Bryan Bishop <kanz...@gmail.com> >> I was wondering whether or not there is a way to express mating >> constraints in OpenCASCADE and pythonOCC. > > OpenCASCADE does not come with any mating constraints system. What about assemblies in general? The SLDPART file format, for instance. You mean SLDASM? The SolidWorks file format is proprietary (as well as Catia CATPRoduct one, Autodesk inventor etc.) and binary. It's then impossible to get any infromation from it. But one can consider there are 2 main issues: - the way the mates are described (not so difficult), - the mate solver (much more difficult). For instance, just being able to ensure that 'there's a solution' would already be a novelty. - Bryan Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
