On Wed, Nov 20, 2002 at 03:57:53PM -0800, [EMAIL PROTECTED] wrote: > For starters, what I'm looking to configure is quite different. > But that's good. If we can get a couple fairly diverse setups going, > that should hopefully make it better prepared for whatever people will want > to throw at it. > > My vision is such: > Hold Alt: > proxies appear, no iconized or listskip windows > Press mouse buttons on proxies repeatly: > browse through windows by raising and lowering them > Release Alt: > proxies go away > > Since I have no title bars, Alt also gives me a quick look at what > I've got, and whether my VIM files are modified or not. Even with > title bars, this would show all the obscured titles too. I'll tap > Alt just for it's own sake. > > To me, alt-tab is secondary. While I'll certainly set it up, it's > not really in my habit. With my tiny HH keyboard, I can move my mouse > nearly without lifting my wrist. Alt-tab-tab-tab just takes more time > and attention.
Yeah, I prefer to use "Alt-cursorkey" with the Direction command too. It's much faster and more intuitive. > The Config file looks very manacing, but I'll concede that you win on the > ability to use core Next/Prev functions. Actually, that is why I put this all in the defaults file. The normal user should not have to worry about it but can just add his commands to the predefined functions. Except the select function that is. It is currently just a copy of WindowListFunc. > Not really because of the code > redundancy issue, but by configurability. I'll just have to make sure the > ordering is something reasonable (left-to-right?), not seemingly arbitrary > like the creation order. I'd like to trim it down some. > > First of all, I don't think there should be a default FvwmProxySelectFunc. > What if I don't want to raise or I don't want the mouse to move. Then terminate the proxy session with the "Abort" command instead of "Hide". > Then I have to DestroyFunc and start from scratch. Undoing defaults > sounds very distasteful. > Can we just have FvwmProxy call FvwmProxyMarkFunc with a special ID > (is 0 used?) when ever Show/Hide/Abort is called? Then we could drop > those three, at least the default UnsetEnv calls. We might need something > more in the Circulate function. The env var must be already set when the Circulate function is called. The stored window id is taken as the starting point for the conditional command. The env var is used to communicate the currently hilighted window to fvwm so the circulation commands can work with it. > The simple properties I added are the same as internal defaults, so we can > dump those. > > As for the syntactic sugar, I kinda like > > AddToFunc MySelect > + I WindowId $w Raise > + I WindowId $w WarpToWindow 50 50 > > *FvwmProxy: Action Select Function MySelect > > over an implied function to add to. Is my recent infatuation with > the Action syntax misplaced? It's just a duplicate of the equivalent *FvwmProxy: SelectCommand Function MySelect we don't need it twice. > Referencing the previous email: Please quote the mails you are referring to. It is very tredious to cross read two emails. > 2) I don't see WindowListFunc in ConfigFvwmWinList or it's man page. > Not in the man page for FvwmWindowLister either. I hope that isn't > the convention we intend to follow. Too much to doo in too little time. We document everything, but not necessarily while we are fiddling with the design. > 3) Unless I'm missing something, no one is suggesting overriding > user settings. Mikhael suggested that. > I think things like width should have defaults in > the module if no one has set it in any config. I don't see any good > reason for simple properties in the ConfigProxy file. Right. The "*FvwmProxy: ..." lines do not need to be in there. > 4) If the default behavior is to do nothing, then I don't really > see any problem with supplying a cut&paste in the man page. > I'd much prefer that to a config file the naive user may not enen know about. > I really want to trim down the demonstrated config so that it isn't > a big deal. The point is that the average user should be able to use the module without worrying about configs at all. And just think of the default config file as the built-in default in a separate file. The situation is no different if the defaults are hard coded, except that you then can not change the defaults easily as a sysadmin. [snip] > 6) Mouse actions should have defaults. This is how WinList does it > and it seems to work fine. Now for FvwmProxy_Circulate, I'm guessing > most people need to cut&paste the keyboard config explicitly if they want > to use Alt-Tab anyhow, so what's two more lines? Well, as a user, I would understand what key f1 x y someaction does, but I would not understand why I need AddToFunc foobar + I SetEnv FvwmProxy_S $w The latter is not user friendly. > Since you have to start from scratch anyhow if you want to remove any > part of the default, I'd much prefer to very clearly spell out the > default in the man page and people can build their own versus manipulating > through additions to something they don't see. What if the naive user is > assumming that FvwmProxyMarkFunc is a blank placeholder or don't realize > that the AddToFunc doesn't clear the elusive defaults. Of course this will all be explained in detail in the man page, with clear instructions what to do if you want to start from scratch. By the way, the naive user can safely assume that FvwmProxyMarkFunc is an 'empty' placeholder that has some internal logic to make sure the ...Circulate function can be used. > 7a) Ok, as long as Next order is reasonable and we can make > FvwmProxy_Circulate into something pretty. I don't think it needs to be pretty. Simply explain the interface in the man page. It is quite easy to understand. > 8) I don't think I added any Module without reading the man page first. > I'd lean towards just the man page. Now if there's a global .fvwm2rc > that the sysadmin can edit, by all means. I would be surprised if this > happens much. I expect two groups. Either nearly all defaults or tweak > every detail, all on a per-user basis. Personally, I don't know anyone > using fvwm2 who isn't a compulsive tweaker. Defaulters probably just stay > with KDE (not that I want to alienate the curious). Keep in mind that we want to make using fvwm easier in the future. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
