Migration Gtk+2/Gtk+3 Toolbar Button Spacing & Input Widget Size Differences
##### How do you think Inkscape could be improved? General Notes for Gtk+2/Gtk+3 Migration Related to Default Widget Sizes Reading the development page regarding the upcoming 1.0 release and the current push to migrate Gtk+2/Gtk+3 brings with it a host of spacing issues that will be exceedingly acute for Inkscape with its use of numerous buttons, toolbars and inputs. The required screen real-estate for default sized widgets in Gtk+3 is roughly 200% of Gtk+2 in the applications I've worked with causing toolbars, etc.. that used to easily fit to ellipsize and spill off-toolbar. The default height of inputs like input-boxes, font-selections, etc.. are likewise much larger. All are side effects of discarding the Gtk+2 themes in favor of the Gtk+3/.css model. This will likely cause usability issues for laptop users as well as notable display difference for long time Inkscape users. This is not unique to Inkscape, but may impact the usable drawing area more so than it would with a text editor or browser. If I had an easy answer, I would offer it, but it boils down to finding some way to impose size limitation on the buttons and inputs where in general those will be subject to users Gtk+3 theme. However, what all Gtk+3 themes I have tried (and I've tried just about all of them looking for one that makes Gtk+3 usable, compared to the hundreds of well-behaved Gtk+2 themes) The problem being that where the button and input sizes were fairly generic and standard in all Gtk+2 defaults and themes, with Gtk+3, the defaults are significantly larger than Gtk+2 and virtually no Gtk+3 theme to date provides any modification of these defaults. I don't know how far along in the migration you guys (and gals) are with Inkscape, but getting on this issue early and setting up formal QA testing of how these sizing issues will effect Inkscape will save a great deal of both user and developer grief when the Gtk+3 version is ready for widespread testing. I wish you all the best in the migration and if I stumble across additional information that may help mitigate the sizing issues, I'll bring it to you here.
issue