On 16.04.2010 19:39, Yuki KODAMA wrote: > On Fri, Apr 16, 2010 at 04:36, Steve Borho <st...@borho.org> wrote: >> On Thu, Apr 15, 2010 at 2:26 PM, Yuki KODAMA <endflow....@gmail.com> wrote: >>> On Thu, Apr 15, 2010 at 23:12, Steve Borho <st...@borho.org> wrote: >>>> There's been some discussions on the Mercurial users list about >>>> starting a PyQt port of TortoiseHg. If we decide to go this route, I >>>> have a few suggestions. >>>> >>>> 1) We mark the current GTK dialogs as "done" in thg-1.1 and switch >>>> tortoisehg/hgtk to pure maintenance mode. >>>> 2) The hgtk app should be given logic to allow switching between GTK >>>> and Qt versions of each command >>>> 3) The Qt port should start with the functionality in hgcmd.py and >>>> hgthread.py; including colors and progress >>>> 4) Then we can start with UI mockups of the GTK apps; only without our >>>> existing warts. >>> >>> Very interesting, I just read the thread of this topic on hg-user ML. >>> Does your second suggestion mean that we should have a common >>> interface to use Mercurial's features from UI codes of PyGTK and PyQt? >> >> Not necessarily. I'm not terribly interested in maintaining API >> compatibility between ports. If we start a PyQt port, the intent >> should be for it to eventually replace the GTK port entirely. I >> suggest the hgcmd functionality as a starting point so that we learn >> the necessary lessons about threading and interfacing between >> Mercurial with PyQt up front, before designing more complicated >> dialogs. Also, a nice command shell window can "paper" over missing >> GUI functionalities, making the PyQt version usable sooner. > > I understood, thanks! > 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 ------------------------------------------------------------------------------ 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
