On Wed, Sep 9, 2009 at 3:47 AM, Adrian Buehlmann<adr...@cadifra.com> wrote: > On 09.09.2009 10:37, Adrian Buehlmann wrote: >> On 09.09.2009 09:47, Peer Sommerlund wrote: >>> 2009/9/8 Adrian Buehlmann <adr...@cadifra.com <mailto:adr...@cadifra.com>> >>> >>> On 07.09.2009 09:07, Peer Sommerlund wrote: >>> > 2009/9/5 Adrian Buehlmann <adr...@cadifra.com >>> <mailto:adr...@cadifra.com> <mailto:adr...@cadifra.com >>> <mailto:adr...@cadifra.com>>> >>> > >>> > # HG changeset patch >>> > # User Adrian Buehlmann <adr...@cadifra.com >>> <mailto:adr...@cadifra.com> <mailto:adr...@cadifra.com >>> <mailto:adr...@cadifra.com>>> >>> > # Date 1252154524 -7200 >>> > # Node ID 8a7ed1a1e34cc6f270fbdf97e3b04286a306f996 >>> > # Parent af6783dea990d29938756f997301b31132b1b0d8 >>> > thgmq: put toolbar on top, using horizontal layout >>> > >>> > This patch is in the official repo as cset de8a545808ca >>> > >>> > >>> > On my system, using GTK 2.10, I get an exception >>> >>> I assume you meant PyGtk 2.10 -- not GTK 2.10 >>> >>> >>> Well, I'm using GTK 2.10 and PyGtk 2.10 :-) >> >> Ugh. I'm sorry, but I don't get that smiley. >> >>> I have no idea how things would work out if I mixed GTK and PyGtk versions. >> >> Since this PyGtk, Gtk, Gtk+ and whatever library copse is still >> not yet entirely clear to me, I started to concentrate on PyGtk, assuming >> this is our interface (not GTK directly). >> >> I wasn't aware that PyGtk and Gtk do lockstep releases. But that >> probably makes sense, if PyGtk is just an add-on layer to Gtk. >> >> So I gather that PyGtk and Gtk always have the same number before >> and after the first dot in the release number. Great. >> > > Oh. Hmm. http://www.pygtk.org/about.html tells me that: > > "The current version of PyGTK requires at least GTK+ version 2.8.0" > > Current stable release of PyGTK seems to be 2.14 (according to > http://www.pygtk.org/downloads.html). > > So I can combine PyGTK 2.14 with GTK+ 2.8.0 ? > > But having GTK+ 2.8.0 requires what minimum version of PyGtk?
It's all rather convoluted as you found, complicated by the fact that on Windows the PyGtk releases seem to lag the GTK+ releases. On the other side of the fence, Qt does full releases 3-4 times a year, and has a bad habit of breaking backward compatibility. Their GUI builder tools default to using features that are only available in that particular release of Qt. It presents it's own challenges. -- Steve Borho PS: I've pretty much dropped any pretense of doing a Qt port of THG, since we've worked around nearly all of the GTK+ warts I cared about. If I had to do it over again I would pick Qt, but that is not an option today. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
