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? If we move to PyQt, we won't bother Windows theme problem anymore :-) And INADA Naoki (TortoiseBZR maintainer) said some custom GUI components can be shared. FYI: PyQt may support Windows 7 feature: "Jump List" (in 4.7?) [1]. At least, 4.5 has limited support of "Aero Glass" feature [2]. [1] http://qt.nokia.com/developer/qt-roadmap [2] http://labs.trolltech.com/blogs/2009/09/15/using-blur-behind-on-windows/ -- Yuki KODAMA ------------------------------------------------------------------------------ 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
