On 17 September 2011 15:22, Martin Renold <[email protected]> wrote: > That branch looks quite straight-forward so far. However I can't get glade > to run under debian, maybe I will need to recompile glade myself. I keep > getting this error: > > (glade:5469): GladeUI-CRITICAL **: Unable to load module 'gladepython' from > any search paths > > Debian only gives me /usr/lib/glade3/modules/libgladepython.so
Which versions are you running? FWIW, I'm using glade 3.8.0-0ubuntu1 libglade2-0 1:2.6.4-1build1 libgladeui-1-11 3.8.0-0ubuntu1 python-glade2 2.22.0-0ubuntu1.1 and it's libgladeui-1-11 that provides my libgladepython.so. Squeeze's ought to work, hopefully, or you could grab natty's 3.8 version and try to build that. With the fact that glade 3.8 is the last stable gtk2-supporting version of glade, and glade 3.10 is the first stable gtk3, we may want to move on gtk3 support sooner rather than later. Maxy, Jon: what do you think? You're supposed to be able to install them side by side: presumably that's what happening here for the upcoming stable releases: http://packages.debian.org/libgladeui wheezy: libgladeui-1-9 & libgladeui-2-0 http://packages.ubuntu.com/libgladeui oneiric: libgladeui-1-11 & libgladeui-2-0 Hopefully we could get a glade-loaded main UI into master and use that as a way of having to touch less code during our own gtk2 → gtk3 transition. But I think I'd like to do some testing first to see whether GtkBuilder XML files can be reused across GTK versions or migrated automatically, and whether the implied promise of those multiple versions actually holds within a glade 3.10 shell. The windows of opportunity align, hopefully :) > I think glade can also be used for only one window or two, to ease the > transition? Yep. At the moment I'm just wrapping up individual widgets to see what's needed (and because it's quite simple to do). I'm thinking we'd start by GtkBuilder-ifying the main UI, loading it up front, then moving the "window" module loader outside gui/layout.py but leaving each module to init itself at first. Later on the sub-modules can maybe use some interface to expose their gui XML to the central GtkBuilder instance and get their callbacks bound into their own namespace. BTW, splitting out the custom widgets and making them testable in a standalone faction seems to be the right pattern during gladeifying, and it's probably a good thing for the overall health of our code too :) -- Andrew Chadwick _______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
