Re: FVWM: GSoC 2012: Project ideas
On Thu, 16 Feb 2012 11:06:46 + Thomas Adam tho...@fvwm.org wrote: Now that 2.6.0 is out, I'm proposing the following project (some of which are a continuation from previous GSoC proposals) -- none of which are listed in any order. * Style clean-up (Difficulty: Easy): This would involve thinking about the internal state of styles. At the moment, we've a complete bomb-site in fvwm/styles.c in the form of a huge case statement which is responsible for dishing out random code to act on windows. I'd like to see this mechanism replaced with something more like a dispatch-state, involving stucts and callbacks. I've very tentatively started this here: https://github.com/ThomasAdam/fvwm/commits/ta/style-cmd-tweaks I think I get the gist of what you want to do there. Have you thought of using a hash table or tree in place of the a,b,c,d thing? I'll admit I don't use nearly everything fvwm has to offer, so forgive me if some of my next comments betray this ignorance ;) * Finer-grained style matching (Difficulty: Medium): Currently there is no direct way to match specific components of windows when putting styles to them -- the only way you can do this at the moment is through clever ordering of style lines. This project would therefore flesh out ideas to allow for specifiers for which window to match based on a windows's name, class, resource, or icon name. Perhaps in the form: Style (Name=xteddy,Class=XTeddy) Sticky Would class here be a new (optional) aspect of the fvwm syntax? * Unification of window commands/states to provide a consistent interface (Difficulty: Hard) This change is huge though, and would need more discussion. It implies to me a lot of drastic changes to the way the way the configuration is currently. Are you sure that is a good idea? MK -- Enthusiasm is not the enemy of the intellect. (said of Irving Howe) The angel of history[...]is turned toward the past. (Walter Benjamin)
FVWM: Google Summer of Code
Hey gang. I'll be eligible for GSOC this year. I recall that Thomas has been interested previously, but did not get the application in or did not qualify. I'm not familiar with the fvwm source, but it's been my WM of choice for about a decade, I work a lot in C, and have done a few very minor things with xlib. In any case, if you are interested, I believe the application for organizations begins on Feb. 27. http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Mark E. -- Enthusiasm is not the enemy of the intellect. (said of Irving Howe) The angel of history[...]is turned toward the past. (Walter Benjamin)
FVWM: override alt-tab
How can I disable the default alt-tab calling a window list? Alt-tab is performs tab-completion in midnight commander, except fvwm grabs it. I tried: Key Tab A M Nop which disables the window list popup but does not return control of the key to an application. -- MK halfcountp...@intergate.com
FVWM: alt-ctrl f-keys doesn't work
Recently alt-ctrl F1-8 to drop into a VT stopped working; I don't use this everyday so I am not sure when, but I believe it was after installing 2.5.28 -- going back to 2.5.26 didn't help tho, so I am not sure. Have there been any reports of this? -- MK halfcountp...@intergate.com
Re: FVWM: Google Summer Of Code 2010
On Sat, 30 Jan 2010 17:01:15 + Thomas Adam thomas.ada...@gmail.com wrote: Well, I am no where near coming up with a list of proposals, so I wouldn't get too enamoured with the TODO list. It's still very early days, but I'll keep your name on my list. Just to make sure, which TODO list are you referring to here: the one that comes with the 2.5.28 source? Or something more recent? -- MK halfcountp...@intergate.com
Re: FVWM: fullscreen focus problem
On Thu, 07 Jan 2010 14:22:38 +0100 Zoilo Gomez zo...@xs4all.nl wrote: It looks as though some applications (vlc, xine, etc) still pass the click to the window which allows the client to accept focus. Thus, although you have NeverFocus set, it's not doing it's job properly. I do not understand what you mean - in any case there is no mouse click or so. I would guess that if you are using, eg, SloppyFocus, even tho you do not have to click on the app, fvwm must pass a focus window event to the application, which is what would happen if you had to click to focus. Of course with NeverFocus this should not happen. In fact, you *do not say that the VLC window takes focus* -- you just say the Flashplayer window loses it. Is that correct? If so, I would say that is a choice made by the flashplayer -- when it goes out of fullscreen, it gives up focus -- probably when recalculating the geometry, the mouse is considered to leave. Then it focusses again when it recieves the appropriate window event notification (when you move the mouse *back into* the window). The fact that the mouse is already in the window does not count, since we cannot be continually sending this signal -- it only happens when the mouse enters (SloppyFocus) or you click inside. -- MK halfcountp...@intergate.com
Re: FVWM: Panning on large virtual X Display
On Tue, 8 Dec 2009 23:48:22 + Thomas Adam thomas.ada...@gmail.com wrote: 2009/12/8 MK halfcountp...@intergate.com: On Tue, 8 Dec 2009 21:45:39 + Thomas Adam thomas.ada...@gmail.com wrote: 2009/12/8 Peter Daum gator...@yahoo.de: larger display. With the newer graphics card/driver, the virtual statement You probably want to set Viewport in xorg.conf as well. Um, didn't the next line explicitly say in the X server configuration? Eh? Well, the OP refers to setting the Viewport in the X server configuration, and then you tell him to set the viewport in the X server configuration. So someone just said VERY CLEARLY what they had done, and that it does not work. He is right. You apparently border on illiterate. None of the big DE's -- KDE, gnome, XFCE -- (or the WM's they use) support it, no matter what your hardware. I guess the idea just never caught on well enough, and is slowly becoming obsolete. Call it devolution. Which part of you can still scroll in the way you were wanting was it that didn't make it across as being clear? Illiterate: one who cannot comprehend written information. Which part of virtual viewports DO NOT WORK WITH ALL HARDWARE and that this is an Xorg issue, not a FVWM issue, did you not understand? -- MK halfcountp...@intergate.com
Re: FVWM: Panning on large virtual X Display
On Tue, 8 Dec 2009 21:45:39 + Thomas Adam thomas.ada...@gmail.com wrote: 2009/12/8 Peter Daum gator...@yahoo.de: larger display. With the newer graphics card/driver, the virtual statement You probably want to set Viewport in xorg.conf as well. Um, didn't the next line explicitly say in the X server configuration? Anyway, sorry Peter -- I think you are out of luck. I have had the same experience before. This is not really a fvwm issue, it is with the various xorg drivers. Eg, I just put in a new ATI 3D card because I have to do some openGL work. No more virtual viewport! And the thing has a cooling fan and 1Gb of memory on it! None of the big DE's -- KDE, gnome, XFCE -- (or the WM's they use) support it, no matter what your hardware. I guess the idea just never caught on well enough, and is slowly becoming obsolete. Call it devolution. -- MK halfcountp...@intergate.com
