[Pythonocc-users] pythonocc october cleanup - Part 1: the mailing list

Hi, The current mailing list is a legacy of the forge that hosted first pythonocc developments. It's time to move to some more modern usergroup management system. The new place to discuss about pythonocc is now: http://groups.google.com/group/pythonocc/about. Posts will be sent to the following e

Re: [Pythonocc-users] Pythonocc and IronPython

> > Just as CPython - uses the C API to run python code > jelle feringa thank you for replying. What do you think about using ironclad? from its google project home it claims "Ironclad basically works by reimplementing the Python C API in C#, and performing a little bit of underhanded trickery to

Re: [Pythonocc-users] Pythonocc and IronPython

> Anyone knows if is there any chance to use pythonocc on Ironpython? Alas - nope… Just as CPython - uses the C API to run python code, jython and iron python use the JVM and .NET runtime respectively. So that makes it fully incompatible. -jelle ___

[Pythonocc-users] Pythonocc and IronPython

Hello, I am a new Pythonocc user. I was able to install and use pythonocc both on win7 and Ubuntu, and it looks a good work, an easy to use and stable wrapping. I tried to use Pythonocc with IronPython http://ironpython.net/ and Ironclad http://code.google.com/p/ironclad/ but I got an error related

Re: [Pythonocc-users] pythonocc-0.6-beta tagged

=== >> ERROR: test_pnt (kbe_unittest.TestVertex_Point) >> -- >> Traceback (most recent call last): >> File "D:\pythonOCC4OCE12\src\unittest\kbe_unittest.py", line 88, in >> test_pnt >> self.asse

Re: [Pythonocc-users] pythonocc-0.6-beta tagged

ttest.py", line 348, in failUnlessEqual > if not first == second: > File "d:\Python26\lib\site-packages\OCC\KBE\base.py", line 158, in __eq__ > return self.IsEqual(other) > TypeError: in method 'TopoDS_Shape_IsEqual', argument 2 of type > &#x

Re: [Pythonocc-users] pythonocc-0.6-beta tagged

--Ran 79 tests in 2.346s FAILED (errors=2) From: tpav...@gmail.com Date: Mon, 6 May 2013 14:28:44 +0200 To: pythonocc-users@gna.org Subject: [Pythonocc-users] pythonocc-0.6-beta tagged Hi, After a lot of Jelle's recent work was merged, I tagged pythonocc-0.6-beta. Here is a s

[Pythonocc-users] pythonocc-0.6-beta tagged

Hi, After a lot of Jelle's recent work was merged, I tagged pythonocc-0.6-beta. Here is a summary of recent changes: CHANGES FROM 0.6-alpha2 to 0.6-beta - massive examples clean-up and fixes - improvements to the KBE subpackage - fixes and improvements to the viewer - updated trait support to 4.3

[Pythonocc-users] pythonocc-0.6-alpha2

Dear all, pythonocc-0.6-alpha2 was just tagged. Changes from 0.6-alpha : * fixed GEOM wrapper * added InnoSetup script for Win packaging * fixes in the CMake builder * added Airfoil example * added native OSX cocoa-support (succesfully tested with PyQt and wxPython on OSX 10.6.8/Cocoa) * fixed loc

Re: [Pythonocc-users] pythonocc and 3D printers blog

> Is the PyRAPID source code still available somewhere. I know an early > version was on github. Also a blog post on progress would be very > interesting. Alas, no. I've started a startup in DK ( odico.dk ) where we're commercial zing the technology ( which has radically changed since then )

Re: [Pythonocc-users] pythonOCC on Windows 7 issues

on files as well as the > GEOM wrapper. Current master should compile without any problem. However, I > can't reproduce the through_section crash. > > Regards, > > Thomas > > > _____

Re: [Pythonocc-users] pythonOCC on Windows 7 issues

ough_section crash. 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

Re: [Pythonocc-users] pythonOCC on Windows 7 issues

unittest.TestTopologyBuilding) ... Test: face > ok > test_prism (topology_building_unittest.TestTopologyBuilding) ... Test: > prism > ok > test_through_sections (topology_building_unittest.TestTopologyBuilding) > ... Test: through sections > > > ... after which I get a pop up &

Re: [Pythonocc-users] pythonocc and 3D printers blog

Kene Meniru wrote: > Just wondering, is Pycado still in development or is the source available? Just did a basic search and found it. Sorry to bother anyone. :-) -- Kene :: kemen...@gmail.com ___ Pythonocc-users mailing list Python

Re: [Pythonocc-users] pythonocc and 3D printers blog

Thomas Paviot wrote: > Dear all, > > Guillaume Florent just started a new blog dedicated to pythonocc basics : > http://pythonocc.wordpress.com/. > Thanks this is very good information. I am very surprised with such a good software there is very little or difficult-to-find examples about it (

Re: [Pythonocc-users] pythonocc and 3D printers blog

gt;> >> Thomas >> >> >> _______ >> Pythonocc-users mailing list >> Pythonocc-users@gna.org >> https://mail.gna.org/listinfo/pythonocc-users >> >> > > _

Re: [Pythonocc-users] pythonOCC on Windows 7 issues

est.TestTopologyBuilding) ... Test: through sections ... after which I get a pop up "python.exe has stopped working" Regards,Vin From: tpav...@gmail.com Date: Tue, 2 Apr 2013 08:55:26 +0200 To: pythonocc-users@gna.org Subject: Re: [Pythonocc-users] pythonOCC on Windows 7 issues 2013/4/2 Vi

Re: [Pythonocc-users] pythonOCC on Windows 7 issues

2013/4/2 Vin Yovanovich > I installed pythonOCC from master (3/28/2013) using a OCE 0.12 which I > compiled from sources. > Hi Vin, Thank you for this report. > There were some issues with linking at one project so I had to comment in > Sketcher.i code > With "some issues", do you mean many

[Pythonocc-users] pythonOCC on Windows 7 issues

I installed pythonOCC from master (3/28/2013) using a OCE 0.12 which I compiled from sources. There were some issues with linking at one project so I had to comment in Sketcher.i code /*%nodefaultctor Sketcher_GUI;... %extend Sketcher_GUI { void _kill_pointed() { delete $self; }};*/

Re: [Pythonocc-users] Pythonocc build question

module installed in the right place. So, how do I change the >> install location? > > Hello, > > This looks like a bug in CMakeLists.txt, python2.6 is hardcoded at > l. 94. Edit this file and replace python2.6 by python. > > Denis > &g

Re: [Pythonocc-users] Pythonocc build question

2013/3/19 D. Barbier > On 2013/3/15 Cavendish McKay wrote: > > Hello, > > > > I'm starting out with pythonocc and have a basic question about > > installing. I'm assuming it's because I'm not very familiar with cmake. > > I'm building on OS X 10.8. Everything builds just fine, but in the > > i

Re: [Pythonocc-users] Pythonocc build question

On 2013/3/15 Cavendish McKay wrote: > Hello, > > I'm starting out with pythonocc and have a basic question about > installing. I'm assuming it's because I'm not very familiar with cmake. > I'm building on OS X 10.8. Everything builds just fine, but in the > install step, the python files are goi

[Pythonocc-users] Pythonocc build question

Hello, I'm starting out with pythonocc and have a basic question about installing. I'm assuming it's because I'm not very familiar with cmake. I'm building on OS X 10.8. Everything builds just fine, but in the install step, the python files are going in /Library/Python/2.6/site-packages/OCC S

Re: [Pythonocc-users] pythonocc and 3D printers blog

t; Best 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

[Pythonocc-users] pythonocc and 3D printers blog

Dear all, Guillaume Florent just started a new blog dedicated to pythonocc basics : http://pythonocc.wordpress.com/. Glad to see that someone finally started something we should have done for a while. Guillaume needs some feedbacks or suggestions, feel free to contact him or comment his posts to s

Re: [Pythonocc-users] pythonocc-0.6-alpha tagged

how this went? > I just built it myself ( dont forget to run "make -j 8" where 8 is the nr of > cores on your machine... ) and this went very smooth. > > Curious to hear from you, your feedback is important to us with the 0.6 being > immenent. > > -jelle > &

Re: [Pythonocc-users] pythonocc-0.6-alpha tagged

hi Jay, So, if you build from source ( Thomas mail mentions binaries ), On Wed, Feb 13, 2013 at 5:28 PM, Jay D. Martin wrote: > I also thank you for all of your efforts. > > I have a (hopefully) very simple problem. > > I grabbed the latest source and ran cmake-gui to set my specific > installa

Re: [Pythonocc-users] pythonocc-0.6-alpha tagged

om/p/pythonocc/. > The issue tracker : https://github.com/tpaviot/pythonocc/issues > The tar.gz source code : > https://github.com/tpaviot/pythonocc/archive/0.6-alpha.tar.gz > The .zip archive source code : > https://github.com/tpaviot/pythonocc/archive/0.6-alpha.zip > > Happy

Re: [Pythonocc-users] pythonocc-0.6-alpha tagged

Thanks for your work Thomas. I appreciate it! I downloaded the alpha version. I'll let you know if I see anything funny. So far, it works well. - Charles ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/py

[Pythonocc-users] pythonocc-0.6-alpha tagged

Dear all, I'm pleased to announce that I just tagged the very first pre-0.6 release known as "0.6-alpha". The previous pythonocc stable release (0.5) is two years old. Did the pythonocc projet sleep for two years? Not really, here is what happened, and what is going to happen from now. 1. Depend

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 46, Issue 8

very very nice job indeed excellent documentation too !!! Stéphan On Wed, 2012-10-24 at 12:00 +0200, pythonocc-users-requ...@gna.org wrote: > Send Pythonocc-users mailing list submissions to > pythonocc-users@gna.org > > To subscribe or unsubscribe via the World Wide Web, visit >

Re: [Pythonocc-users] PythonOCC for interference checking?

il.gna.org/listinfo/__pythonocc-users <https://mail.gna.org/listinfo/pythonocc-users> ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users ___ P

Re: [Pythonocc-users] PythonOCC for interference checking?

ce? Can PythonOCC be used for > this? > > Thanks! > Steve > > __**_ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/**pythonocc-users<https://mail.gna.org/listinfo/pythonocc-users> > ___

[Pythonocc-users] PythonOCC for interference checking?

Has anyone used PythonOCC to do interference checking? That is, to see if solids in an assembly "overlap", or have some area(s) where one shape "collides" or takes up part of another shape's space? Can PythonOCC be used for this? Thanks! Steve ___ Pyt

Re: [Pythonocc-users] pythonocc reference api/ tutorial?

> > and...practically speaking: How do I do CSG with 2d-shapes, e.g. Union > of two Geom2d_Circle? > build edges from these, and just use the boolean_fuse from OCC.Utils.Construct -jelle ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://m

[Pythonocc-users] pythonocc reference api/ tutorial?

Hello *, is there a reference api besides http://api.pythonocc.org/ - which is quite commentless and therefore still leaves a lot of room for questions. Or is there even an tutorial? Or is all documentation to be based on OCC-doc? How to get it, if I don't want to give them my personal data? and.

Re: [Pythonocc-users] pythonOCC boolean issue

Would someone mind trying to duplicate my pythonocc issue? At least I can discover whether I have a setup problem, or if this is a real pythonocc bug. I have tried pure pythonocc code (skipping the Utils.Construct module) but I still have the same issue. Thanks. - Charles

[Pythonocc-users] pythonOCC boolean issue

Hi, I started using pythonocc 0.5 a couple weeks ago, and I like it. I ran across an issue this morning with boolean operations. Basically, cutting a diamond shape from a cylinder creates a messed up solid in pythonocc (some of the cylinder border is missing and some of the diamond has been

Re: [Pythonocc-users] pythonOCC perfomance

Pythonocc-users@gna.org <mailto: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 ___

Re: [Pythonocc-users] pythonOCC perfomance

times slower if I turn off the gc and > about 10 times if I turn it on. > > Does anybody have any perfomance tips to make the pythonOCC code faster? > > István > > _______ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https:

[Pythonocc-users] pythonOCC perfomance

Hi, I made some tests with pythonOCC and with the pure C++ OCE. According to my measurements the 'same' code in python is about 10 times slower than the C++ code. For example the following python code: for i in xrange(1): p = gp_Pnt(0,0,0) face = BRepBuilderAPI_MakeFace(gp_Sp

Re: [Pythonocc-users] pythonocc TOT build failure on mac osx SL

Hi guys, I was successful in installing OCE and PythonOCC. I however want to run the graphical examples so I need to install PyQt4. I installed it through macport, but the python versions have got mixed up (it seems, macport installed py26-pyqt4 for python2.6.1, which got installed in mac osx's py

Re: [Pythonocc-users] pythonocc TOT build failure on mac osx SL

> > >> >> swigging >> /Users/jayesh/git/pythonocc/src/wrapper/SWIG_files/linux_darwin/Poly.i to >> /Users/jayesh/git/pythonocc/src/wrapper/SWIG_files/linux_darwin/Poly_wrap.cpp >> swig -python -O -c++ -DHAVE_LIMITS_H -DHAVE_CONFIG_H -DCSFDB >> -w302,401,314,509,512 -DOCC_CONVERT_SIGNALS -outdi

Re: [Pythonocc-users] pythonocc TOT build failure on mac osx SL

2011/10/5 Jayesh Salvi > Hi, Hi Janesh, > > I am trying to build top of tree versions from OCE and PythonOCC > repositories on Mac OSX Snow leopard. OCE built fine. Under pythonOCC, I > built and installed Geom lib successfully, but SMESH failed to install. I > get following error: > > [ 49%]

Re: [Pythonocc-users] pythonocc TOT build failure on mac osx SL

On Wed, Oct 5, 2011 at 12:20 PM, jelle feringa wrote: > I am trying to build top of tree versions from OCE and PythonOCC >> repositories on Mac OSX Snow leopard. OCE built fine. Under pythonOCC, I >> built and installed Geom lib successfully, but SMESH failed to install. >> > > That's not really a

Re: [Pythonocc-users] pythonocc TOT build failure on mac osx SL

> > I am trying to build top of tree versions from OCE and PythonOCC > repositories on Mac OSX Snow leopard. OCE built fine. Under pythonOCC, I > built and installed Geom lib successfully, but SMESH failed to install. > That's not really a surprise; SMESH is a fortran lib that is hard to compile,

[Pythonocc-users] pythonocc TOT build failure on mac osx SL

Hi, I am trying to build top of tree versions from OCE and PythonOCC repositories on Mac OSX Snow leopard. OCE built fine. Under pythonOCC, I built and installed Geom lib successfully, but SMESH failed to install. I get following error: [ 49%] Building CXX object CMakeFiles/SMESH.dir/src/SMESH/SM

Re: [Pythonocc-users] pythonocc collaborators - Join us on GitHub.

by Denis >>>> Barbier), >>>> > which is perfectly suitable for projects like the one we're working on. >>>> > >>>> > At last, don't be afraid of git. It may look a bit scary, but it's >>>> really a >>>> > better friend than subversion. Let me know is you wish to join the >>>> > 'Collaborators' team. It's open to any of you willing to >>>> contribute/share >>>> > code. >>>> > >>>> > Best 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

Re: [Pythonocc-users] pythonocc collaborators - Join us on GitHub.

of the one from OCE (designed and setup by Denis >>> Barbier), >>> > which is perfectly suitable for projects like the one we're working on. >>> > >>> > At last, don't be afraid of git. It may look a bit scary, but it's >>> really a &

Re: [Pythonocc-users] pythonocc collaborators - Join us on GitHub.

> which is perfectly suitable for projects like the one we're working on. >> > >> > At last, don't be afraid of git. It may look a bit scary, but it's >> really a >> > better friend than subver

Re: [Pythonocc-users] pythonocc collaborators - Join us on GitHub.

eally > a > > better friend than subversion. Let me know is you wish to join the > > 'Collaborators' team. It's open to any of you willing to contribute/share > > code. > > > > Best 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

Re: [Pythonocc-users] pythonocc collaborators - Join us on GitHub.

Me please. Am 18.08.2011 22:03 schrieb "Thomas Paviot" : > Dear all, > > Please let me know if you would like to be part of the pythonocc > 'Collaborators'. Being a collaborators enables creating private development > branches that can be merged into the master branch. > > git allows really efficie

[Pythonocc-users] pythonocc collaborators - Join us on GitHub.

Dear all, Please let me know if you would like to be part of the pythonocc 'Collaborators'. Being a collaborators enables creating private development branches that can be merged into the master branch. git allows really efficient workflows compared to subversion. Moving from svn to git requires

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

Sorry. I'm still learning the packaging. Due to GEOM-integration some packages seem to be broken currently. I'm trying hard to fix this A.S.A.P. Apologies, Henning Am 13.08.2011 23:40 schrieb "jelle feringa" : >> >> Please help me, I did the procedure and I got the PythonOCC-0.5 installed >> with

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

; hello Lie, >> >> I advise strongly against importing all OCC modules! >> These could take a really long time to load. >> Can you run the examples? >> That provides us meaningful feedback. >> >> -jelle >> >> ___ >> 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

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

strongly against importing all OCC modules! > These could take a really long time to load. > Can you run the examples? > That provides us meaningful feedback. > > -jelle > > _______ > Pythonocc-users mailing list > Pythonocc-users@

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > Please help me, I did the procedure and I got the PythonOCC-0.5 installed > without errors, but it seems my Python (2.6.5) doesn't know the module > (from OCC > Import *). Am I doing something wrong? > hello Lie, I advise strongly against importing all OCC modules! These could take a really l

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

Thomas Paviot writes: > > > 2011/7/28 Henning Meyer > > > > Hello, > I build pythonocc-0.5 ppa for Ubuntu natty and oneiric (lucid and > maverick currently building):https://launchpad.net/~hmeyer/+archive/pythoncad > To get them: > sudo apt-add-repository ppa:hmeyer/pythoncad > sudo apt-get

Re: [Pythonocc-users] pythonocc is moving to github

> > +1 for github usage! > github is amazingly slick, a bit shocking how coarse google code is with hindsight... ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users

Re: [Pythonocc-users] pythonocc is moving to github

___ > 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

Re: [Pythonocc-users] pythonocc is moving to github

> > The pythonocc project hosting forge is currently moving from googlecode/svn > to github. This decision was took a few days ago, after a positive > experience with the OCE project, git, and github. > One of the key reason why we decided to move to git is that dealing with branches in svn is jus

[Pythonocc-users] pythonocc is moving to github

Dear all, The pythonocc project hosting forge is currently moving from googlecode/svn to github. This decision was took a few days ago, after a positive experience with the OCE project, git, and github. The first step of this move has been achieved: the googlecode subversion repository has been e

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > Also I made minor changes to (mostly) build files, is there some way >> these changes could be reviewed and merged? >> > > You can post patches here on this forum as attachments, or open an issue on > the google code project page (the latter is better). > < better than that, you've got committ

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

2011/8/8 Henning Meyer > GEOM is now included in ppa:hmeyer/pythoncad for lucid, maverick, natty. > Unfortunately no GEOM support for oneiric, as oneiric ships with > opencascade-6.5, which is currently not supported by GEOM. > The latest svn revision of GEOM trunk compiles with OCC up to 6.5.1.

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > > GEOM is now included in ppa:hmeyer/pythoncad for lucid, maverick, natty. > this is great news! > Unfortunately no GEOM support for oneiric, as oneiric ships with > opencascade-6.5, which is currently not supported by GEOM. > Anybody out there, who is willig to fix it? > with PythonOCC 0.6

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

GEOM is now included in ppa:hmeyer/pythoncad for lucid, maverick, natty. Unfortunately no GEOM support for oneiric, as oneiric ships with opencascade-6.5, which is currently not supported by GEOM. Anybody out there, who is willig to fix it? Also I made minor changes to (mostly) build files, is the

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

t;http://code.google.com/p/pythonocc/issues/detail?id=37> > > ? > > > > thanks, > > > > -jelle > > ___ > 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

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

Sorry - no experience regarding pypi packager or win-installer... Am 01.08.2011 09:58 schrieb "jelle feringa" : >> >> Build problem circumvented (was 2.7 related). We now have packages for >> lucid and maverick (2.6) as well as for natty oneiric (2.7). >> > thanks Henning, this work is *much* appre

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

One remark: I disabled GEOM & SMESH due to ease and missing knowledge about their importance. What's the priority of including both? Am 01.08.2011 09:58 schrieb "jelle feringa" : >> >> Build problem circumvented (was 2.7 related). We now have packages for >> lucid and maverick (2.6) as well as for

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > Build problem circumvented (was 2.7 related). We now have packages for > lucid and maverick (2.6) as well as for natty oneiric (2.7). > thanks Henning, this work is *much* appreciated! have you got any comments / ideas on the following matter

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

this project needs, and it seems you are more >> > than qualified to provide this. >> > Would you feel for it? >> > Thanks for your contribution, >> > -jelle >> > ___

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > Please don't feel kept under pressure by Jelle: he's so enthusiastic. > oops, there I go again... i mean well guys ;) ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

more > > than qualified to provide this. > > Would you feel for it? > > Thanks for your contribution, > > -jelle > > _______ > > Pythonocc-users mailing list > > Pythonocc-users@gna.org > > https://mail.gna.org/listinfo/pyth

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

honocc-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

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

> > Thank you for this important contribution > +1 Henning, can we make you the official ubuntu maintainer of pythonocc? Solid distribution is what this project needs, and it seems you are more than qualified to provide this. Would you feel for it? Thanks for your contribution, -jelle _

Re: [Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

2011/7/28 Henning Meyer > Hello, > > I build pythonocc-0.5 ppa for Ubuntu natty and oneiric (lucid and > maverick currently building): > https://launchpad.net/~hmeyer/+archive/pythoncad > To get them: > sudo apt-add-repository ppa:hmeyer/pythonc

[Pythonocc-users] pythonocc-0.5 ppa for Ubuntu

Hello, I build pythonocc-0.5 ppa for Ubuntu natty and oneiric (lucid and maverick currently building): https://launchpad.net/~hmeyer/+archive/pythoncad To get them: sudo apt-add-repository ppa:hmeyer/pythoncad sudo apt-get update sudo apt-get install python-occ Feedback welcome. If it works out w

Re: [Pythonocc-users] pythonocc 0.6 release scheduled for end of august

> > > So, what are the ambitions for the following release? > >- #1 switch to OCE >- #2 the OCC.KBE module offers a high level, well structured pythonic >API >- #3 Henrik Rudstrøm has done a great job in providing excellent sphinx >based documentation, I'd love to see this proje

[Pythonocc-users] pythonocc 0.6 release scheduled for end of august

hi All, Its been a while since we've seen a pythonocc release. The reason why is that the pythonocc core developers have been working hard launching the OCE initiative. OCE is a repository where the open source OCC developers share their patches / bugfixes etc. OCE

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 30, Issue 13

> >coordinates so I can approximate them with lines. However, I'm having > >trouble figuring out exactly how I would go about doing this. I'm using > >QuickMesh to make the triangles, vertexes, normals, etc. for display right > >now, but I can't find something simil

[Pythonocc-users] PythonOCC related blog entry

Dear all, An interesting blog entry on FuelYourProductDesgin.com, dealing with the Web, new browser generation, CAD and pythonocc: http://www.fuelyourproductdesign.com/googles-chromebook-and-what-it-means-to-product-designers/ Have fun, Thomas ___ Pyth

Re: [Pythonocc-users] pythonocc

2011/4/10 tog > Hi Thomas, > >> > >> Is that correct ? > > > > Yes for the firs two points, not for the last one (we did not develop any > > "plugin"). > > > Oops sorry, I had in mind the addons (FEM, KBE, ...) > > >> > >> Would that be possible to reuse part of step 1 for other programming > >>

Re: [Pythonocc-users] pythonocc

? Any plant to move to oce ? Cheers Guillaume >> >> -- >> PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net >> >> _______ >> Pythonocc-users mailing list >> Pythonocc-users@gna.org >> https://mail.gna.org/listinfo/py

Re: [Pythonocc-users] pythonocc

___ > 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] pythonocc

Dear all, I had a brief look into pythonocc as my understanding is that it is made of (please correct me if I am wrong): - a tool to generate swig .i file out of header files from OCC and SALOME (GEOM, SMESH) - some higher (more pythonic) APIs based on the previous ones - some plugins: FEM,

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 28, Issue 16

sorry to say that Jelle, but in the examples gp_XOY() is > > called, not > > > > > > Which example exactly? > > > > > > -jelle > > > > ___ > Pythonocc

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 28, Issue 16

Hi Thnaks for your help. In Level_1/geometry/geometry_demos Groeten Stéphan On Mon, 2011-03-21 at 10:49 +0100, jelle feringa wrote: > sorry to say that Jelle, but in the examples gp_XOY() is > called, not > > > Which example exactly? > > > -jelle _

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 28, Issue 16

> > sorry to say that Jelle, but in the examples gp_XOY() is called, not > Which example exactly? -jelle ___ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 28, Issue 16

Hi to all sorry to say that Jelle, but in the examples gp_XOY() is called, not gp().gp_XOY(), after a wild import. what should I understand then ? Stéphan, who feels stupîd On Sat, 2011-03-19 at 12:00 +0100, pythonocc-users-requ...@gna.org wrote: > Send Pythonocc-users mailing list submissions

Re: [Pythonocc-users] pythonOCC and GEOM/SMESH modules

repos as far as I > understand, intended to users contribution. A bit messy, no? > > 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

Re: [Pythonocc-users] pythonOCC and GEOM/SMESH modules

2011/1/29 Pierre JUILLARD > Hi Thomas, hi Jelle, > > I don't know if you heard about the initiative of Christophe on the "Open > Salome Community Edition" that was talked on the Salome forum here: > http://www.salome-platform.org/forum/forum_14/525157487/view > http://opensalome.org/ > > I was th

[Pythonocc-users] pythonOCC and GEOM/SMESH modules

Hi Thomas, hi Jelle, I don't know if you heard about the initiative of Christophe on the "Open Salome Community Edition" that was talked on the Salome forum here: http://www.salome-platform.org/forum/forum_14/525157487/view http://opensalome.org/ I was thinking that maybe it could interest you as

Re: [Pythonocc-users] pythonOCC-0.5 released

2011/1/25 Bill Bedford > On Tue, 25 Jan 2011 21:36:56 +0100, Thomas Paviot wrote: > > 2011/1/25 Bill Bedford > > > >> Down loaded the precompiled pythonOCC-0.5 of OSX today and got error:- > >> > > > > The precompiled binaries were generated from my MacBook Pro on top of the > > default python2.

Re: [Pythonocc-users] pythonOCC-0.5 released

On Tue, 25 Jan 2011 21:36:56 +0100, Thomas Paviot wrote: > 2011/1/25 Bill Bedford > >> Down loaded the precompiled pythonOCC-0.5 of OSX today and got error:- >> > > The precompiled binaries were generated from my MacBook Pro on top of the > default python2.6. Importing those libraries with pyth

Re: [Pythonocc-users] pythonOCC-0.5 released

2011/1/25 Bill Bedford > Down loaded the precompiled pythonOCC-0.5 of OSX today and got error:- > The precompiled binaries were generated from my MacBook Pro on top of the default python2.6. Importing those libraries with python 2.7 fails. You have to compile your own pythonOCC with your python

Re: [Pythonocc-users] pythonOCC-0.5 released

Down loaded the precompiled pythonOCC-0.5 of OSX today and got error:- >>> from OCC.Display.SimpleGui import * >>> set_backend('x') >>> display, start_display, add_menu, add_function_to_menu = init_display() Traceback (most recent call last): File "", line 1, in File "/Library/Frameworks/Py

Re: [Pythonocc-users] pythonOCC-0.5 released

ease. Best 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

[Pythonocc-users] pythonOCC-0.5 released

Dear all, pythonOCC-0.5 is available for download at http://www.pythonocc.org. The .tar.gz source archive was uploaded a couple of days ago, just the time for me to package binary files for Windows before making this announcement. Here is a shortlist of changes coming with this release (376 svn co

[Pythonocc-users] Pythonocc-users Digest, Vol 26, Issue 5 message 1

4:32:36 +0100 From: Petar Subject: Re: [Pythonocc-users] Pythonocc-users Digest, Vol 25, Issue 37 To: pythonocc-users@gna.org Message-ID: <4d21cff4.2010...@cadcam.hr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 30.12.2010. 22:15, pythonocc-users-requ...@gna.o

Re: [Pythonocc-users] Pythonocc-users Digest, Vol 25, Issue 37

e:///jelle.db', echo=True) Base = declarative_base(bind=engine) Session = scoped_session(sessionmaker(engine)) s = Session() from OCC.BRep import BRep_Tool bt = BRep_Tool().Pnt for indy in s.query(Individual): print indy.id for i in Topo(indy.brep).vertices(): print bt(i).Coord()

  1   2   3   >