| Has anybody been thinking about introducing something like TCL in
| fvwm. To me it looks like most current fvwm commands can be translated
| directly to TCL commands. This would automatically add
Heavily programmable window managers have been done before, without
huge amounts of success. If one wants to try again, I strongly suggest
using a language that's as good and as clean as possible (not TCL;
perhaps Python).
In the context of fvwm, I suggest using the language as an extension
mechanism instead of the core of the window manager. Look at things that
just can't be done in fvwm right now and see if you can make it possible
to program them in the extension language. I doubt that many people want
to complicate their configuration files by having to write them in a
language.
I would also suggest that one start by writing a module wrapper such
that one can write fvwm modules in the language. That would be a useful
way to add various pieces of functionality and to let you experiment
with what sorts of language bindings were needed to allow for useful
features. Bonus points for making the result use as little memory
as possible, given that one selling point of fvwm over other window
managers is memory usage.
- cks
--
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 Apr 30 1998 - 18:41:16 BST