On 7 May 97 at 17:28, Michael Tiefenback <Michael Tiefenback
<tiefen_at_mgt.jlab.org>> wrote:
> Why would you want to make a terminal application into an fvwm module? It
> would appear to me (lowly nonprogrammer that I am) that you would prefer
> to modify the underlying application to take special actions when the
> button is clicked. Like what xterm does with <Ctrl><Mouse-1/2/3>.
> Couldn't you put the desired features of xterm back into rxvt more easily
> than taking the decidedly specialized action of relying on fvwm?
I never knew xterm did special things with the <ctrl><Mouse-1/2/3>!
But, this does not give the functionality that they user wants. He
wants buttons in the title bar area (that is controled by fvwm) to
execute scripts inside the rxvt window. To extend the rxvt program
to do these features would make the window larger since I would have
to basically put a menu bar area that would have buttons on it.
Also, to have the configurability that the user wanted would take
quit a bit of added programming. Therefore, it seemed to me to be
easier to make it into an fvwm module that gets the M_String message
from fvwm and sends it to the shell that is in use. Since fvwm
already handles configureable buttons and popup menus, I would not
have to do as much programming (Okay, I'm lazy!).
Also, I do not know X programming yet. Therefore, I could make these
changes without having to learn a new programming environment (I
believe. I have not dived into the rxvt code yet!).
Richard A. Guay
Network Administrator and ASIC Design Engineer
ASIC International Inc.
rag_at_asicint.com
http://www.asicint.com
--
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 Thu May 08 1997 - 10:52:59 BST