2011/1/7 Henrik Rudstrom <hrudst...@googlemail.com> > Hello all, > I've been watching this thread from the sideline for a while, very > interesting thread, but i havent had time to share my thoughts yet. so here > we go. > Although the idea of a standardized api across platforms and all the > possibilities for collaboration/online services has a lot of potential, i > think it will become a very big undertaking and i agree with Dave that we > should limit our scope and start simple. > > Although im not against it, i see some dangers with building a new api on > top of open cascade, even if we start with a very delimited scope; it will > be a lot of work to develop our own set of sematics (the OMG CAD looked > interesting though, but i got the impression that opencascade has much more > functionality than what is covered by OMG) > It will be difficult to cover everything in a consistent manner, so the > risk is having still the granular c++ like opencascade api with some apis > built on top that are good for some purposes but not all, this can make it > very daunting for new users (and still for me) to figure out when i can use > a nice abstracted function or when i have to go down to 'pure' opencascade. > Mostly when the high level api subject comes up on the list it seems that > most of the issues people have are with the programming paradigms of > OpenCascade, not necessary the semantics of opencascade. In my opinion, if > we could strip away all c++ artifacts of opencascade i think the semantics > of opencascade as it is is quite decent. > > A while back i was playing around with pygccxml (a c++ parser that can be > used for code generation) to get an idea of what could be done to make > opencascade more user friendly without having to manually write all the > wrappers. There are quite a lot of things that could be done with the > wrappers to make them more compact and 'pythonic' without manually writing > all the code: >
BTW, the pythonOCC SWIG files *are* generated from pygccxml. I didn't write all these files manually! Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
