2012/3/31 Stefan Champailler <[email protected]> > This in an interesting proposal. > > But, for having had to have a look inside Shiboken and all that stuff, > I'd say what's missing most is documentation. There's a lot of it, but a > walkthrough, from beginning to end would be very nice. For example, the > ownership stuff is not crystal clear, there are a lot of corner cases > which, I felt, are not documented enough for people like me who : > - are pretty fluent in programming Python and C++ > - but are not familiar with the way the bindings work between Python and > C++ > > I know documentation is not the funniest part but that would really help > people like me, outside the PySide core team, to be able to be > autonomous without having to work/read for days before understanding a > bit of what is happening... > > I hope I don't sound too harsh, that's not my point, I use PySide a lot > now and as a product it is really good and reliable. It's just that when > I meet a bug it's very hard to dive into the Shiboken code and get a > grasp of what's happening. Especially when one knows that it is not that > complicated... > > So the tool would be nice, but it has to make the inner workings of the > binding tools very clear. So I see that tool has something to help me to > more easily understand and fix PySide. > > (and again I love PySide :) I'm very grateful of having such a tool for > free) > > Stefan >
Thank you for your attention, I will try my best to implement such a tool.
_______________________________________________ PySide mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/pyside
