I've started a page about this on the wiki:
http://live.gnome.org/SessionManagement
-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Tommi Komulainen wrote:
On 9/13/06, Brian Nitz [EMAIL PROTECTED] wrote:
Why do we ever log out?
4) Free up resources. ???
Reason 4 is especially interesting for multiuser systems, especially
thin clients. It might be interesting for embedded uses of GNOME
(laptop/child, maemo...)
Ray Strode wrote:
* XSMP does a number of useful session-managey things (logout
notification, logout cancellation, specifying apps that
should be restarted right away if they crash, specifying
commands to run at logout, etc) which we currently have no
On 9/13/06, Brian Nitz [EMAIL PROTECTED] wrote:
Why do we ever log out?
4) Free up resources. ???
Reason 4 is especially interesting for multiuser systems, especially
thin clients. It might be interesting for embedded uses of GNOME
(laptop/child, maemo...) to reduce resources when
On Wed, 2006-09-06 at 17:57 -0400, Dan Winship wrote:
* XSMP does a number of useful session-managey things (logout
notification, logout cancellation, specifying apps that
should be restarted right away if they crash, specifying
commands to run at logout, etc)
On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
I do think the XSMP state-saving model is absurd and should be ignored,
however, even if XSMP is used for logout notification.
yeah, I would even completely remove the state saving thing :-)
In fact, how many GNOME apps do the
On Mon, 2006-09-11 at 11:35 +0200, Rodrigo Moya wrote:
On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
I do think the XSMP state-saving model is absurd and should be ignored,
however, even if XSMP is used for logout notification.
yeah, I would even completely remove the
Rodrigo Moya wrote:
On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
I do think the XSMP state-saving model is absurd and should be ignored,
however, even if XSMP is used for logout notification.
yeah, I would even completely remove the state saving thing :-)
In fact,
Il giorno lun, 11/09/2006 alle 10.59 +0100, Ghee Teo ha scritto:
In fact, how many GNOME apps do the state-saving correctly (whatever
that means)?
Out of the top of my head, gnome-terminal. It remembers the working
directories of various gnome-terminal.
Other example is said,
Il giorno lun, 11/09/2006 alle 12.30 +0200, Kjartan Maraas ha scritto:
What is the rationale for not just saving the documents and letting
logout proceed?
Saving means to destroy the data which is currently in the file with the
one in the open buffer, so doing it without confirmation is not
Bastien Nocera wrote:
On Mon, 2006-09-11 at 11:35 +0200, Rodrigo Moya wrote:
On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
I do think the XSMP state-saving model is absurd and should be ignored,
however, even if XSMP is used for logout notification.
yeah, I
Bastien Nocera wrote:
I know quite a few that do, and I spent a lot of time adding the
feature, and fixing it in Totem. I don't think that removing it would be
a good idea, unless there is a way to recycle that feature into an
application-specific state saving.
What would be wrong from a
Havoc Pennington wrote:
I don't think you're crazy, but can I suggest a good approach might be:
- start from what the user benefits / scenarios are
- figure out in a top-down way what API we'd like _apps_ to have
- then figure out how to implement that or something like it
Well, I would
Dan Winship wrote:
But as you also said, XSMP is policy-free
I meant more to say policy-free in ironic quotes ;-)
* The Save current state checkbox at logout will now
say something like Restart the currently-running
applications the next time I log in.
Havoc == Havoc Pennington [EMAIL PROTECTED] writes:
Havoc Same for gedit - I think I'd like gedit to just remember window
Havoc state for all documents, per-document. I can't imagine ever
Havoc setting up gedit and then saving my desktop globally though,
Havoc as XSMP supports.
Waaay back when
Hi,
* XSMP does a number of useful session-managey things (logout
notification, logout cancellation, specifying apps that
should be restarted right away if they crash, specifying
commands to run at logout, etc) which we currently have no
other
In the last year or so, it's become fashionable to suggest ripping
XSMP out of GNOME and moving to a new, improved, simpler, presumably
dbus-based session management system. I'd like to argue that that's a
bad idea, and we should fix gnome-session and GnomeClient while still
sticking with XSMP.
Hi,
Here are the relevant specs btw:
http://www.xfree86.org/current/ice.pdf
http://www.xfree86.org/current/xsmp.pdf
http://www.xfree86.org/current/ICElib.pdf
http://www.xfree86.org/current/SMlib.pdf
(many distributions install these files with X)
(There are now a couple other more modern
18 matches
Mail list logo
