Re: FVWM: Session management.

Brian <[email protected]>
Newsgroups gmane.comp.window-managers.fvwm
Organization Home
Message-ID <[email protected]>
On Mon, 2 Oct 2017 14:59:29 +0100
Thomas Adam <[email protected]> wrote:
....
> WM_COMMAND has been deprecated by the ICCCM2 for some time now.
Interesting to know.
....
> All in all, there's no session manager support in WindowMaker, but it
> tries its best to do whatever it can internally.
Similiar to what FVMWSave and FvwmSafeDesk were doing then, but still
not real session management.
....
> The problem with FvwmSave and FvwmSaveDesk was just that -- there's
> only a small subset of ways which they can try and work out the
> mapping between window and process which is what WM_COMMAND is
> supposed to do, *provided* the application sets that.
Which is what you've been trying to help everyone understand 
through this whole thread.
....
> Now, it could be argued that we could put some additional work into
> something better/different which recreates FvwmSave---but it's going
> to be a lot of work for not a lot of real gain, IMO.  Indeed, if you
Agreed this is a matter of application developers not following
standards to provide a real session manager not a failing on FVWM's
part to be EHWM or ICCM2 compliant.  The application aren't providing
the required information so that FVWM can implement any session
manager and get the full expectation of what Didier is asking. 
....
> Session managers that FVWM can talk to do have to conform to some
> rules -- that was true in the past with XSM/GNOME/KDE, but GNOME/KDE
> has changed a lot, and FVWM hasn't kept up, and I haven't looked to
> see what work could be involved in fixing this, or if it's even
> possible to use these session managers separately.
Can a person still  refer to your Linux Gazette article from 2004
about XSM for FVWM and get session management?
....
> I hope my explanations here help you understand the situation with
> FVWM, and why it's perceived to be working in other window managers
> (but is still fundamentally broken).
That you have done significantly and thoroughly.  Thank you again for
your dedicated support to FVWM.  
I'm looking forward to the next version of FVWM and seek your archives
regularly to find out how to continue to customise this wonderful
Window Manager.   FVWM is my favourite WM and I'm glad you clarified
that it is not a museum piece of code only.  I'm hoping some others
will relent in letting you continue to correct code issues and remove
code which is redundant or even no-longer pertinent and can be
accomplished by add-on software, like a session manager. 
--------------------------------------

Cheers
Pax tecum, absit iniuria;
BrianA_MN

Addendum:
A: Because it makes understanding the conversation harder!
Q: What is wrong with top replying?

.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.