On 6/3/11, Ethan Grammatikidis <eeke...@fastmail.fm> wrote:
> I don't get it... Back & forward are native to the browser, running programs
> is native to any WM of FVWM's era, and app-specific buttons are a native
> feature of FVWM, and fairly simple to use as FVWM features go. What am I
> missing?
>
Having every maprequest checked to see if it's from surf, in which
case <back forward> buttons are to be drawn, or if it's from {mplayer
or VLC} in which case a <play/pause> button is to be drawn, etc,
instead of the surf executable containing the relevant information.
Having this in the WM means loading rules for *all* clients that
/might/ be run, at startup. Unless app-specific buttons work
differently than I think.
