Session Management Considerations

[Neil Stevens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday May 04, 2002 06:18, Matthias Ettrich wrote:
> Suggestions very much welcome. Does the new scheme look simpler, more
> logical to you? Will users get the three choices in KDM? Any
> alternative suggestions?

OK, it looks anything but simpler to me, but I think it's better.  The 
trick will be to make a good UI for it.

I have two suggestion.

1) Make the defaults act like previous KDE versions.  First, in a 
kconf_update script, copy the current KDE 3.0 session to the KDE 3.1 last 
session if the KDE 3.0 save button is checked, and to the KDE 3.1 saved 
session otherwise.  Then, have a bare call to "startkde" load "saved" if 
it exists, and "last" otherwise.  This way a user who already has KDE 
setup will have to do *nothing* to update to the new system.

2) For those who don't want that default behavior, give explicit access to 
the different sessions.  I'd name the startkde options like this:

startkde --session=no (bare KDE)
startkde --session=last
startkde --session=saved
startkde --session=foo (whatever names c' users give their alternate 
sessions)
startkde --session=choose (pop a graphical session chooser)

- -- 
Neil Stevens - neil at qualityassistant.com
"I always cheer up immensely if an attack is particularly wounding
because I think, well, if they attack one personally, it means they
have not a single political argument left." - Margaret Thatcher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE80+d5f7mnligQOmERAohXAJ9gw+KVkwE3VGlRllUAyxDwdD0pSgCggw9P
VpD1cBps+pQuDSQFG3YOCvo=
=fzMG
-----END PGP SIGNATURE-----