Re: FVWM: HEADS UP: Releasing 2.6.4 end of January
| what patches do you write which you maintain then? At the moment the only meaningful patch I've made to fvwm is one to position new icons at the mouse cursor instead of where they normally go (I think the window's top left if you don't have an iconbox set up, but I forget). In the past I had more modifications but they've gradually become unnecessary over the years[*]. (People tried to help me with a Style-based approach to doing this icon positioning, but I never could get it working completely (the comments in my fvwmrc suggest that I couldn't get positioning of windows with explicit icon position hints correct). So at some point I punted and went for the code change as the easiest approach for getting my personal environment working. Have chainsaw, can blindly hack code I run myself. There's a discussion of this in the fvwm archives from a year or two ago.) - cks [*: for example, one large one was to make windows placed by button 3 automatically grow to the bottom of the screen. When I migrated to fvwm 2.5.x, I believe the mailing list showed me how do this with existing fvwm features.]
Re: FVWM: HEADS UP: Releasing 2.6.4 end of January
Chris Siebenmann writes: > | what patches do you write which you maintain then? > > At the moment the only meaningful patch I've made to fvwm is one to > position new icons at the mouse cursor instead of where they normally go > (I think the window's top left if you don't have an iconbox set up, but > I forget). In the past I had more modifications but they've gradually > become unnecessary over the years[*]. > > (People tried to help me with a Style-based approach to doing this > icon positioning, but I never could get it working completely (the > comments in my fvwmrc suggest that I couldn't get positioning of windows > with explicit icon position hints correct). So at some point I punted > and went for the code change as the easiest approach for getting my > personal environment working. Have chainsaw, can blindly hack code I > run myself. There's a discussion of this in the fvwm archives from a > year or two ago.) There is one built in iconbox, starting at the upper left as you observed. An iconbox line for style "*" replaces the built in box with one or more boxes. I use 2 narrow style "*" boxes, one going down the right, then another going across the bottom. I create another iconbox for style "Tkremind" to position Tkremind's icon in a specific place. Mouseplacement for an icon sounds unpleasant. -- Dan Espen
Re: FVWM: HEADS UP: Releasing 2.6.4 end of January
| > At the moment the only meaningful patch I've made to fvwm is one to | > position new icons at the mouse cursor instead of where they normally go | > (I think the window's top left if you don't have an iconbox set up, but | > I forget). [...] [...] | Mouseplacement for an icon sounds unpleasant. Possibly I'm used to it from years of using twm before fvwm, but it just makes sense to my mind and my fingers. When I iconify something that has a real icon, I want its icon to be right there where I expect it and can find it. Then I'll move it to some place that makes sense to me; I am strong on spatial organization of iconified things[*]. Of course this is one good reason for it to be and remain a personal patch; I can't expect other people to think about icons and icon layout the way I do. - cks [*: people who like such things can be horrified by the screenshot at http://utcc.utoronto.ca/~cks/space/blog/sysadmin/MyDesktopTour ]
