> How about adopting a policy like apache's modules? Certain things can
> have a secondary code module compiled in. Something like fvwm-modules,
> only closer to the core, where starting a new process wouldn't be feasable
> (ie, window decorations)
This is approximately what I was suggesting. It sounds like the modules
that you want to use are dynamically loaded, while I was just suggesting
a well defined interface so that you could add a block of code at compile
time.
> I've not looked heavily at the code, so I don't know if this is a
> minor adjustment, or a major coding-job.. Either way, I'd be willing to
> work on it...
Major code overhaul. The current behavior of Fvwm is implicitly hardcoded
in almost all parts of the code.
ericb
--
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 Aug 25 1997 - 11:17:23 BST