>>>>> "BAW" == Barry A Warsaw <bwarsaw_at_CNRI.Reston.VA.US> writes:
BAW> I was thinking about a framework where you could start a module up at
BAW> init time, have it hang around long lived, and have fvwm send it
BAW> command strings based on user configuration.
....
BAW> That's fine. What I would do is add a new command to fvwm, that would
BAW> have the following interface:
BAW> SendToModule <module> <string>
BAW> This would generate a new packet type and send it only to the module
BAW> in question.
....
Boy Barry, I don't know...this is the second suggestion you've had
which is already on the TO-DO list... ;^)
- Add way to send arbitrary messages from fvwm to a module, eg
'Send ModuleName "command string"' or something similar.
BAW> What I'm thinking about is a long lived Python helper module which
BAW> would react to these commands, updating its state, sending new
BAW> commands back to fvwm, importing Python modules as needed, etc. I'm
BAW> not quite sure what I'd do with it, but I have a few modules now that
BAW> I use, and for one thing, I'd like to not have to fire up a Python
BAW> interpreter each time. I could easily accomplish this with this type
BAW> of framework.
BAW> Any thoughts?
Only that I hope to actually get this in the next beta release since
it shouldn't be difficult to implement, and that I like your name for
it better than just the arbitrary 'Send' that I had written down
earlier.
Chuck
--
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 Wed May 01 1996 - 11:47:34 BST