On Fri, Aug 12, 2011 at 10:39 AM, <[email protected]> wrote: > On 11 Aug 2011, at 20:48, ext Hugo Parente Lima wrote: > >> I prefer start with a minimal set of functions then adding functions when >> needed/requested, i.e. when we get a good use case justifying the >> implementation. > > I'm not sure this is a good approach for developing public APIs. The > consistency of the module might easily suffer if new features are added. > Also, in this case, we have existing underlying functionality in shiboken > which we just need to expose to Python, and there exists an analogous module > in PyQt to get ideas from.
Among the best practices is collecting database of user stories first and then matching emerging API in PEP against them to see how intuitive and easy it would be. > So, I still strongly prefer reviewing the sip module API and proudly > borrowing relevant items. I quickly went through the doc [1] and many of the > methods would appear to be potentially very useful for PySide developers as > well. Not that I'm any expert, of course. > > [1] http://www.riverbankcomputing.co.uk/static/Docs/sip4/python_api.html -- anatoly t. _______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
