Re: Resizing screens
On 20 April 2011 06:24, Daniel Barkalow barka...@iabervon.org wrote: Due to my laptop developing a flaky panel connector, I recently got an external monitor for it. Switching outputs works great (with xrandr), but now I've got two outputs with different native resolutions, and I'd like to get fvwm to handle this nicely. lib/FScreen.h has always had skeleton code to handle XRandr support. The first thing is that X will now send a ConfigureEvent for the root window of the screen when the size of the screen changes. I wrote up the obvious patch to update Scr and screens[0] in FScreen, and it seems to work. I'm not sure if there's anything more that needs to be done in fvwm to deal with the size of the Screen changing; it seems like the effects are at worst annoying (Windows off of the Screen because it shrank, windows placed relative to the right and bottom not moving) and nothing is relying on the screen size not to change from one X event to another, but I'm sure I'm not testing everything. Are there tricky things I might miss in this area? Yes, it's not the whole story -- it's not enough to react to the ConfigureNotify events. Just let FVWM react to XRandr proper; see above. I ought to resurrect my patches to do this, it was very easy and worked for me at the time. -- Thomas Adam
Re: fvwm 2.6.1 - error with make deb-inplace
Hi Thomas! On Tue, Apr 19, 2011 at 3:54:00 PM, Thomas Adam wrote: Not surprising. This hasn't been updated to use DH7. thanks for the info :-) I wish we could simply *remove* this, but we had that conversation in the past [1]. That's the problem in community projects ... some developers are active some not and than it's very difficult to vote about changes ... Best Regards, Thomas Btw thanks for releasing fvwm 2.6 :-) . Perhaps 2.7 is going in a more freshen future ;-) -- Life is like a box of chocolates - never know what you're gonna get. -Ursprüngliche Nachricht- Von: Thomas Adam tho...@fvwm.org Gesendet: Apr 19, 2011 3:54:00 PM An: Thomas Funk t.f...@web.de Betreff: Re: fvwm 2.6.1 - error with make deb-inplace On Tue, Apr 19, 2011 at 03:46:32PM +0200, Thomas Funk wrote: Hi! I've compiled fvwm 2.6.1 tarball on my Debian Lenny with make deb-inplace and get the following output at the end: fakeroot dh_gencontrol -P`cd .. pwd`/inst-2.6.1 dh_gencontrol: Compatibility levels before 4 are deprecated. fakeroot dh_md5sums -P`cd .. pwd`/inst-2.6.1 dh_md5sums: Compatibility levels before 4 are deprecated. fakeroot dh_builddeb -P`cd .. pwd`/inst-2.6.1 dpkg-deb: building package `fvwm' in `../fvwm_2.6.1-0.20110419_i386.deb'. dh_builddeb: Compatibility levels before 4 are deprecated. Not surprising. This hasn't been updated to use DH7. The package works, so it's only an info to Fvwm team ;-) I wish we could simply *remove* this, but we had that conversation in the past [1]. I hence have no intention of caring whether this works or not; it's not my problem per se, but it annoys me this is allowed to sit in the FVWM tree and *bitrot* because the person who wants responsibility for it only ever pops his head out of the parapet when the status quo is challenged on getting it removed in favour of upstream's version. -- Thomas Adam [1] http://www.mail-archive.com/fvwm-workers@fvwm.org/msg01785.html ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar
Re: fvwm 2.6.1 - error with make deb-inplace
On 20 April 2011 09:34, Thomas Funk t.f...@web.de wrote: Btw thanks for releasing fvwm 2.6 :-) . Perhaps 2.7 is going in a more freshen future ;-) There won't be a 2.7 in the same sense of unstable as was the case in 2.5.X -- Thomas Adam
A couple of questions from a Newbie.
Hello , I am trying to build a module using the composite extension of X, mainly xcompmgr functionality for now ... is anyone else interested or have some opinions ? views ? I have a good idéa of the X part, but I have never written a fvwm module before, so any hints are welcome especially if anyone have some problems they can foresee . Also would 2.6.1 or 2.7.x be the correct branch to use ? / regards, Lars Segerlund
CVS dane: * fvwm-menu-desktop.in (interpret_menu): ignore Layout/DefaultLayout elements.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane11/04/19 22:13:16 Modified files: bin: Tag: branch-2_6 ChangeLog fvwm-menu-desktop.in Log message: * fvwm-menu-desktop.in (interpret_menu): ignore Layout/DefaultLayout elements.
Re: A couple of questions from a Newbie.
On Wed, Apr 20, 2011 at 01:25:45PM +0200, Lars Segerlund wrote: Hello , I am trying to build a module using the composite extension of X, mainly xcompmgr functionality for now ... is anyone else interested or have some opinions ? views ? I'm not interested in using it, but I'm wondering how useful a FVWM-specific module would be over just using xcompmgr directly? Mind you, I suppose there's a case for letting it hook in to certain windows, which you can't use with xcompmgr because it's an all or nothing approach. Be very careful with scoping this though -- FVWM is a *reparenting* window manager, not a compositing one. I have a good idéa of the X part, but I have never written a fvwm module before, so any hints are welcome especially if anyone have some problems they can foresee . Take any existing module we have now, and I think there was some tutorial on the fvwmforums about writing modules from scratch, but I've not read it, and can't vouch for its accuracy. I'd rather see FvwmDecorator as a pre-cursor to this; whilst that needs a lot of discussion/design first of all, what's this FvwmCompositor module of yours going to provide in terms of functionality? Also would 2.6.1 or 2.7.x be the correct branch to use ? It doesn't matter. The code is the same. I'd rather you didn't use 2.7.X though. -- Thomas Adam
Re: A couple of questions from a Newbie.
Lars Segerlund lars.segerl...@gmail.com writes: Hello , I am trying to build a module using the composite extension of X, mainly xcompmgr functionality for now ... is anyone else interested or have some opinions ? views ? I have a good idéa of the X part, but I have never written a fvwm module before, so any hints are welcome especially if anyone have some problems they can foresee . Also would 2.6.1 or 2.7.x be the correct branch to use ? 2.6.1. The complete documentation for the module interface is here: http://fvwm.org/documentation/dev_modules.php IMO, the best module to use as an example is FvwmAnimate. What can xcompmgr do for Fvwm?
Re: A couple of questions from a Newbie.
xcompmanager is the 'simplest' compsitioning manager/program you can think of, it only reparents all windows to offscreen storage and renders the visible screen using 'compositioning' ie. OpenGL or similar in order to give effects that is hard to do otherwise. So if you can do what xcompamanger can do, youre on your way to something like compiz or kwin, ie. 3D effects on the desktop or simpler effects. For example transparent windows are easy to do. Provided it is possible to integrate a module tight enough, it should be able to do what the MAC interface or compiz does in desktop effects. I am only doing it to se if I can, and I don't know if I have the time to make it usable. / Lars 2011/4/20 des...@verizon.net: Lars Segerlund lars.segerl...@gmail.com writes: Hello , I am trying to build a module using the composite extension of X, mainly xcompmgr functionality for now ... is anyone else interested or have some opinions ? views ? I have a good idéa of the X part, but I have never written a fvwm module before, so any hints are welcome especially if anyone have some problems they can foresee . Also would 2.6.1 or 2.7.x be the correct branch to use ? 2.6.1. The complete documentation for the module interface is here: http://fvwm.org/documentation/dev_modules.php IMO, the best module to use as an example is FvwmAnimate. What can xcompmgr do for Fvwm?
Re: Resizing screens
On Wed, 20 Apr 2011, Thomas Adam wrote: On 20 April 2011 06:24, Daniel Barkalow barka...@iabervon.org wrote: Due to my laptop developing a flaky panel connector, I recently got an external monitor for it. Switching outputs works great (with xrandr), but now I've got two outputs with different native resolutions, and I'd like to get fvwm to handle this nicely. lib/FScreen.h has always had skeleton code to handle XRandr support. The code there is a bit too skeletal for me to follow; in particular, I think there needs to either be something that updates Scr as well or a lot more code needs to find out the edges from FScreen instead of Scr. The first thing is that X will now send a ConfigureEvent for the root window of the screen when the size of the screen changes. I wrote up the obvious patch to update Scr and screens[0] in FScreen, and it seems to work. I'm not sure if there's anything more that needs to be done in fvwm to deal with the size of the Screen changing; it seems like the effects are at worst annoying (Windows off of the Screen because it shrank, windows placed relative to the right and bottom not moving) and nothing is relying on the screen size not to change from one X event to another, but I'm sure I'm not testing everything. Are there tricky things I might miss in this area? Yes, it's not the whole story -- it's not enough to react to the ConfigureNotify events. Just let FVWM react to XRandr proper; see above. I ought to resurrect my patches to do this, it was very easy and worked for me at the time. I'd like to try them out. -Daniel *This .sig left intentionally blank*
