XfceSMClient design

[Nick Schermer]

I think the implementation in Gtk with be close to QT (and IIRC apple
too): an application class [1] with signals to save the state and quit
and an object for more session specific actions (if there will be
one). So whatever we do with a single session object, it will most
likely never be close to the implementation in gtk.

So I'd say, make a gboject that works for us and don't bother about
Gtk. We can keep the implementation in a private library for as long
as we want. A good start would be a wiki page with the
session-requirements of various applications (ranging from the window
manger, panel, file-manager and terminal), we can most likely split
those in 2 or 3 groups. Then we can figure out which signals/functions
are needed. From that point we can design an api and if we all agree
on that, write the code and use it for as long as possible until the
world decided how session management will look like and maybe they
will even look at our implementation.

Nick

[1] http://live.gnome.org/GTK%2B/ApplicationClass