On Fri, 2004-01-02 at 12:48, Daniel Borgmann wrote:
On Wed, 2003-12-31 at 23:08, MenTaLguY wrote:
Okay, I've removed our gtkmm dependency for now.
Too bad, I really liked gtkmm. :)
Argh, indeed, me too. TT
Now that it seems to be much further away (Bryce talking about up to a year), should we work fullspeed ahead on the interface in C instead of waiting for the Gtkmm transition? I'm mainly thinking about dialogs and the secondary toolbar stuff.
Well, while we'll have to stick with Gtk+'s C API for a while, I'd definitely like to start using C++ features where it's useful to do so, even in the UI code.
I did preserve Spark's close confirmation dialog, although I reworked it a little bit to conform to standard Gtk practice.
Ok... The problem is, while it it's more in line with general Gtk practice at the moment, it's not in line with the HIG, which explicitly suggests to use larger spacing, no separator and no title. :/ But I understand that it's probably more reasonable to wait for Gtk (or the HIG) to be fixed instead of doing such a custom hack as I did.
As a rule I think we should choose standard (non-depreciated) widgets over HIG, since it means less code for us to maintain (and the standard widgets will eventually get fixed for HIG as you say).
( I guess if the standard stuff commits a particularly egregious HIG violation, then it's still worth hacking ourselves -- I think this is more of a cosmetic thing though. )
I'd suggest though to at least change the title just to "Warning", because with the current verbose title, the user practically has to read three sentences. That looks a bit too busy IMO. This is also the standard Gtk practice (in fact, I think it's the standard title if no string is provided).
Ok. Makes sense.
-mental