On Dec 19, 2005, at 8:12 AM, Ralf Stephan wrote:
http://ramnet.se/~nisse/diverse/temp/inkscape_new_prefs_mockup4.png
[...] It would of course require some work to fit this into inkscape but i have done at least 50% already and i'm willing to do the other 50% as well.
Please do so! I don't have the impression anyone other than me is doing Gtkmmification right now, and I'm still at Document Properties [sic].
However, you are advised to subclass your dialog from Inkscape::Dialog::Dialog, which takes care of some signals, the transientizing, and the Close Button for you. On the issue of the Close Button, its existence is controlled by the dialogs.showclose preference which, astonishingly, can nowhere be set in the program, so please add this to the Windows subpage.
Maybe that could be my first patch. Wouldn't it be better to fix that in Inkscape::Dialog::Dialog ? I could add a 'show_ok_button' argument to the dialog ctor which defaults to USE_PREFERENCE, but can also be SHOW_BUTTON or HIDE_BUTTON. Or i could overload the ctor with enum InkscapeButtonsType { BUTTONS_NONE, BUTTONS_OK, BUTTONS_CLOSE, BUTTONS_CANCEL, BUTTONS_YES_NO, BUTTONS_OK_CANCEL, BUTTONS_APPLY_OK_CANCEL, BUTTONS_APPLY_OK, BUTTONS_APPLY_CANCEL };
Dialog(const char *prefs_path, int verb_num = 0, InkscapeButtonsType buttons);
When you have something to look at, I might steal the design/code for Doc Props which is HIG-noncompliant in 13 points at the moment, according to the latest bug report.
I will take some time to familiarize myself with the inkscape code, to prevent me from getting off to a false start. But i will have something to look at in a couple of weeks.
-- Marco