-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI - shift back-end to Gtk::Builder from GladeXML #413
Comments
Original comment by
|
TODOS:
|
That should be OK, as we want them shown in most cases. This will reduce the need for many of the show_all calls, although I expect leaving them be will be harmless so we won't need to audit the code for them unless they show adverse effects. |
From: http://developer.gimp.org/api/2.0/gtk/gtk-migrating-GtkBuilder.html |
That makes sense given some of the other transition docs I've seen. We can break the various components into their own files. These can be located under a bin/ui directory. This process will probably simplify the transition, as the glade file can still be used while parts of it are shifted across. |
The general approach in this looks relevant. |
Currently investigating difficulties when converting 'hboxSpatialPage'. Maybe this is related to the fact that converter cannot handle menu:
|
Converting from Glade to GTK Builder to remove dependency Updates issue #413
Updated by pull request #591 |
Also clean up the logic to check for missing files, as more recent versions of PAR handle that now. Updates issue #413
All the requisite files are now in the ui folder. Move strip_redundant_text.pl across in case it is needed. Updates issue #413.
Otherwise some of the widgets took up too much space. Updates issue #413
Mark as fixed. |
Original issue reported on code.google.com by
shawnlaffan
on 31 Oct 2013 at 4:30The text was updated successfully, but these errors were encountered: