>>>>> "BB" == Brandon Browning <brandon_at_nwnet.net> writes:
BB> An idea struck me that might be possible; but I'm not sure how
BB> much rewrite it would take (most likely a _lot_). Since
BB> #ifdef's are the Achilles Heel of programming (and nobody
BB> really likes them), would it be possible to rewrite some or
BB> all of FVWM in an "Apache" manner, i.e., using "modules" to
BB> implement different features? I don't recall too many
BB> #ifdefs; Apache just "knows" there's a module built in. In
BB> fact, it would allow one to link in, say mini-icons, without
BB> rebuilding the entire FVWM.
I think it's a great idea. I haven't dived into Apache too deeply,
but there's work in the Python community on PyApache, where a Python
interpreter is embedded in the server and Python modules are written
to extend the functionality of the server. Seems to me that Python
has all the necessary bits to make it an excellent candidate for such
a thing in Fvwm. I'm pretty sure it has an Xlib module, and I know it
has higher level toolkits too. The Fvwm core could do the
time-intensive stuff and make calls into the Python interpreter in
response to Fvwm's high level view of events. Fvwm would definite an
API (embodied as a Python module) for useful things like warping the
cursor, moving focus around, (de)iconifing windows, etc. Python
modules could import this and make appropriate calls.
I think it would run pretty fast too since (my guess is that) most of
the overhead in the current Python-Fvwm module interface is starting
up the Python interpreter every time.
-Barry
--
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 Mon Sep 30 1996 - 11:05:22 BST