> Come up with a spec. List all the things that Fvwm should do in the
> window decoration area. Then, we have to figure out how to code it. The,
> we will basically have to overhaul all the code. (which was done for
> textured borders, so it is not impossible....)
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)
In this way, fvwm keeps it's normal (supported) behavior... but if
someone wants a new behavior, they can add it themselves without producing
an entirely new Window-Manager. (ENFVWM (Entirely New-FVWM?))
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...
Thoughts on this?
Jay Kuri
---
Everyone can be taught to sculpt: Michelangelo would have had to be
taught how not to. So it is with the great programmers.
--
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:01:56 BST