GNOME Bugzilla – Bug 588732
should not generate .ui files
Last modified: 2012-12-16 21:28:31 UTC
gtk-builder-convert is just meant as a one-time convertion tool whose results need to be manually checked, not as a tool that you can rely on at build time to get it right. Here is one problem in the generated profile-new-dialog.ui: one of the buttons does not obey the button-images setting. I will attach a fixed .ui file, but of course, you first have to stop regenerating the .ui files from their glade predecessors...
Created attachment 138494 [details] fixed .ui file
I don't agree on gtk-builder-convert being a one-time tool; I certainly don't see any warnings against that in the docs. Furthermore, at the time g-t was converted to GtkBuilder, and also later the last time I checked this, glade-3 was unable to work correctly with the g-t .ui files (they were corrupted on save). Therefore using .ui format natively was out of the question since to me being able to use a UI editor (glade-2 in this case) is essential. I admit that this autogeneration on build causes problems, e.g. bug 553357. Is this a bug in the original .glade file, or is gtk-builder-convert misconverting this file?
You are right that the docs are not too clear on this point. The strongest hint we have is this: A good way to start a migration from libglade to GtkBuilder is to run the <link linkend="gtk-builder-convert">gtk-builder-convert</link> utility on your glade file, and inspect the resulting output. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Anyway, glade-3 handles .ui files very well by now, so the 'no editor' argument is not that convincing anymore.
gnome-terminal 2.33.5 compiled with-gtk=3.0 is still checking for gtk-builder-convert note that gtk 3.0.0 doesn't have that anymore. commit 77ff6992260b19ff04a0823de45142a37532d058 Author: Matthias Clasen <mclasen@redhat.com> Date: Mon Jan 17 09:55:16 2011 -0500 Drop gtk-builder-convert It will still be shipped in gtk 2.24.
I know that. And that commit msg even gives you the hint where to find the script.
*** This bug has been marked as a duplicate of bug 588945 ***