20 April 2014

PyGI AIO 3.12.x for Win32

With the new GObject-Introspection 1.40, gir generation now works with MinGW-W64 CRT and most docstrings issues seems been squashed too. GTK is not on Windows side though, version 3.12.1 looks buggier where an app (in this case gtk3-demo) will lose toplevel window (the one that is native and directed by OS), wish I have screenshot to show (I will). All 3.10  bugs also persist in 3.12, so despite of lots of new features it's really no good at the moment.

GTK 3.12.1 has lots of fixes in the Win32 theme (FYI, it's controlled by compiled-in css files namely gtk-win32*.css) which I tried to backport to 3.8.9 and 3.10.8 with some success, I also made correction on Windows XP specific part. But realized that perfect "theming emulation" is not possible yet with current css feature and event handling.

Overall there are new lots of libraries joined the AIO packages, with over 100 introspected libraries. The 64 bit port is not convincing... In some of my tests GI fail to resolve to existed exported functions of a dll, possibly getting skipped/mangled in the process. At C level, the libraries/apps behave just as good as 32 bit ones, so the problem is pygobject specific here.

Download for Python 32bit at:
http://sourceforge.net/projects/pygobjectwin32/files/

PyGObject homepage:
https://wiki.gnome.org/PyGObject

8 comments:

  1. Thanks for maintaining windows builds!!!!

    you mention:
    New builds version 3.10 started.
    But it doesn't seem to exist on the sourceforge page?
    http://sourceforge.net/projects/pygobjectwin32/files/

    ReplyDelete
    Replies
    1. rev1 was deleted several day after released because issue with the new glib 2.40 when using app class. I'm reverting to 1.38.2 if there is no apparent glib's bugfix release.

      Delete
  2. Ahh that makes sense. I am just trying to figure out if a graphical lag was downto pyGObject or matplotlib.

    thanks again

    ReplyDelete
    Replies
    1. Ohh for the graphics lag, it is still a gtk3 issue since ported to cairo.

      Delete
  3. I suspected it was Cairo related (especially as the GTK3Agg backend does not work for matplotlib atm so GTK3cairo is required).

    Any advice how to improve it or is it something that has to be lived with until it is improved

    ReplyDelete
    Replies
    1. got to live with it I think :( cairo has not released new version for a while too

      Delete
  4. This comment has been removed by a blog administrator.

    ReplyDelete
  5. problem is the "lag" I am experiencing is about 5seconds plus and for a simple 10,000point plot. a 30,000 point plot involving 7 different datasets and the entire drawing is painful.

    I ended up converting to pyQt4 over a weekend.
    Shame I really like GTK and prefered gnome over kde since 98...

    ReplyDelete