Hi Loic, I discovered pythoncascade when looking for a python binding to OpenCASCADE. I was in touch with Sandor Racz, the original author of pythonCascade, but I didn't manage to get his source code. That's why I started my own wrapper, distributed under an open source and free license.
pythonCascade is quite old, and built upon a really deprecated release of OCC (I think it's the 5.2). The 'gallery' page is just a translation to python of the C++ samples provided by OpenCASCADE. A few of these samples were ported to pythonOCC and are available in the pythonOCC samples (TopologicalOperations, LocalOperations etc.). All of the features explained on the gallery page are covered by the pythonOCC samples. But I agree with you: each sample should be described and explained on a web page, with screenshot and comments. Even better: let's write a python script that automagically create those pages by traversing the samples directory! Another point: the original author of pythonCascade used an homemade binding generator (called pythonizer). I don't know the status of this project, but it's certainly far away from state-of-the-art python binding generators like SWIG, Py++, SIP (Qt) or Shiboken (PySide). Cheers, Thomas 2009/12/7 Simon Loic <simon1l...@gmail.com> > Have you heard about this project? > Although it seems to be dead (apparently no update since 2003) , I send you > the link of the project, > http://pythonizer.org/pythoncascade/pythoncascade.html > > In particular, there is an interesting section full of sample codes. > http://pythonizer.org/pythoncascade/gallery.html > > I think, pythonOcc would gain to show what it's capable of in a similar > way. For example one could create an equivalent page on the wiki. A first > step, would merely consist in wrapping the already existing sample directory > (avail on svn). Hence, it would allow for potential users to make their own > idea of what can be achieved with pythonOcc. Besides, I think screenshots > can be an efficient way of explaining several concepts (such as topology vs > geometry) nut this is another story. > > Of course, I am not saying that it is compulsory to have such a gallery, I > just found the idea interesting (to make pythonOcc more visible) and I would > fully understand that pythonOcc developpers/users have other priorities (at > least this is my case ;-)). > Regards, > Loïc > > _______________________________________________ > 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
