On 16.04.2010 23:01, Adrian Buehlmann wrote: > On 16.04.2010 19:39, Yuki KODAMA wrote: >> I'll take a look threading of PyQt tomorrow. > > Great. > >> TortoiseBZR & CuteHg will be helpful resources to learn it. > > I tried to build CuteHg from source, but failed so far. > > The book [1] "Rapid GUI programming with Python and Qt : the definitive > guide to PyQt programming" by Mark Summerfield has infos about threading > in chapter 19. > > [1] http://www.qtrac.eu/pyqtbook.html > > (with a foreword [2] by PyQt creator Phil Thompson) > > [2] > http://ptgmedia.pearsoncmg.com/images/9780132354189/forward/0132354187_Foreword.pdf > > The book is based on Python 2.5, Qt 4.2, and PyQt 4.2 > (current PyQt is v4.7.2) > > I haven't yet understood what's the trick with that API#1 and API#2 thing. > > BTW, it looks like Phil Thompson is already using Mercurial :) > > http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/ChangeLog > http://www.riverbankcomputing.com/hg
Slightly off topic, but Herb Sutter (C++ standard and concurrent programming guru) has a very nice blog entry about concurrent programming: Effective Concurrency: Prefer Futures to Baked-In “Async APIs” http://herbsutter.com/2010/01/17/effective-concurrency-prefer-futures-to-baked-in-async-apis/ A couple of programming libraries and languages have already used that "future" design pattern (Java, upcoming C++0x thread library). Would be nice to find something like a "future" in PyQt as well (if anyone has a pointer, please post!). ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
