"Eddy J. Gurney" <eddy_at_ans.net> writes:
> . It should support multi-headed displays without having to run multiple
> copies of itself. `vtwm' and other window managers can do it, `fvwm2'
> should do it as well.
Yes, it ought to do this. Actually, I thought it did, but I've never
been in a position to try.
> . Likewise, it would be nice if programs like FvwmButtons and FvwmPager
> could support multiple instantiations without having to run a separate
> copy for each button bar/pager/etc.
Why is this important? Don't the multiple instantiations share most
of their memory?
> . The idea of forking a new application to do auto-raise, window list,
> etc. seems totally silly to me.
Yes, some features look silly as modules. Dynamic loading is a good
idea, and nowadays it's reasonably doable. Back in the old days (when
the modules were first introduced) dynamic loading was much more of a
nightmare, and I suspect that's why Robert didn't try to offer that as
a mechanism. (Some things do make sense as separate processes,
though, in the absense of preemptive threading, which is difficult
with Xlib apparently.)
I'd like dynamic lowering too, to remove windows that I'm obviously
not interested in.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri May 29 1998 - 10:15:35 BST