The XSMP spec is more or less impossible to make sense out of. But to the extent people have tried, it has not been a useful undertaking.
Here's one old thread: https://bugzilla.gnome.org/show_bug.cgi?id=79285 There are certainly useful things to do related to session management and state saving, but getting XSMP involved is a good way to fail immediately. Just define what behavior you want and then implement it in a *sensible* way. XSMP is not a sensible way to implement *anything* and in the history of Linux we have never had a reasonable implementation of it. Window managers that do a relatively nice job saving window states have done so with heuristics and hacks and manual configuration, not by relying on specs. They were solving problems in spite of XSMP not because of it. Havoc On Thu, Oct 25, 2012 at 9:25 AM, Alan Cox <[email protected]> wrote: > > > - The session manager which needs to store all this information away > somewhere, and also use it as necessary to restore session state > _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
