[dwm] dwm on tablet pc
Has anyone tried to run dwm on a tablet pc and has a working patch set? I do not have a keyboard (no convertible); therefor: = cellwriter as an onscreen keyboard Kind regards, joten
Re: [dwm] dwm on tablet pc
Try dwm-gtx. Onscreenkeyboards should work with it. :) 2008/12/12, jo...@freenet.de jo...@freenet.de: Has anyone tried to run dwm on a tablet pc and has a working patch set? I do not have a keyboard (no convertible); therefor: = cellwriter as an onscreen keyboard Kind regards, joten -- http://www.gnuffy.org - Real Community Distro http://www.gnuffy.org/index.php/GnuEm - Gnuffy on Ipaq (Codename Peggy)
Re: [dwm] dwm and dualhead
thanks for your approach - but I was not able to compile it (patched
against dwm 5.3.1) it does not find the function usegrab (used in
movemouse and resizemouse...
On Thu, Dec 11, 2008 at 10:59:16PM -0500, Jeremy Jay wrote:
Here's my XRandR and multi-screen patch, its pretty much not what you've
asked for here, but I'll throw it out as a starting point. I haven't
had a chance to test it much, so don't yell at me if your screen
explodes...
one tag for all screens. status bar is only shown on screen 0 (although
this can very easily be set to another screen)
layouts updated for multi-head:
tile: windows are evenly divided among screens.
monocle: one window per screen, all remaining windows on last screen.
Jeremy
On Thu 11 Dec 2008 - 10:18AM, Mate Nagy wrote:
Hiho,
On Thu, Dec 11, 2008 at 09:39:19AM +0100, yy wrote:
on this list and, if somebody finds a great _general_ solution (which
seems difficult, but I would be love to be wrong), I'm sure Anselm
would be glad to include it in the official release.
Just my 2cts,
I don't see anything difficult about this. In fact, awesome generally
gets this right. This is what I want from dwm:
- handle each xrandr screen separately
including all data structures, so different layout, client set,
tagging, etc.
- draw statusbar everywhere (from the same input text)
- have a key-bindable function for:
- changing between screens
- move window to another screen
- do something semi-intelligent when a screen with clients goes away,
e.g. put clients in previous/next screen oslt.
Basically, it should behave as multiple separate dwms, except that
clients can be sent from screen to screen and all dwms have the same
configuration.
Speculation: in this configuration, especially when changing between
screens, moving the mouse pointer to the location of the focus might be
more important/desirable. This might be a compile-time option or patch..
Mate
diff -r 79bf47074a49 config.mk
--- a/config.mk Sat Dec 06 16:20:14 2008 +
+++ b/config.mk Thu Dec 11 22:50:24 2008 -0500
@@ -13,6 +13,8 @@
# Xinerama, un-comment if you want it
#XINERAMALIBS = -L${X11LIB} -lXinerama
#XINERAMAFLAGS = -DXINERAMA
+XINERAMALIBS = -L${X11LIB} -lXrandr
+XINERAMAFLAGS = -DXRANDR
# includes and libs
INCS = -I. -I/usr/include -I${X11INC}
diff -r 79bf47074a49 dwm.c
--- a/dwm.c Sat Dec 06 16:20:14 2008 +
+++ b/dwm.c Thu Dec 11 22:50:24 2008 -0500
@@ -42,6 +42,9 @@
#ifdef XINERAMA
#include X11/extensions/Xinerama.h
#endif
+#ifdef XRANDR
+#include X11/extensions/Xrandr.h
+#endif
/* macros */
#define BUTTONMASK (ButtonPressMask|ButtonReleaseMask)
@@ -52,6 +55,7 @@
#define MAX(a, b) ((a) (b) ? (a) : (b))
#define MIN(a, b) ((a) (b) ? (a) : (b))
#define MAXTAGLEN 16
+#define MAXMONITORS 8
#define MOUSEMASK (BUTTONMASK|PointerMotionMask)
#define WIDTH(x)((x)-w + 2 * (x)-bw)
#define HEIGHT(x) ((x)-h + 2 * (x)-bw)
@@ -206,10 +210,11 @@
/* variables */
static char stext[256];
-static int screen;
+static int screen, mons;
static int sx, sy, sw, sh; /* X display screen geometry x, y, width, height
*/
static int by, bh, blw;/* bar geometry y, height and layout symbol width
*/
static int wx, wy, ww, wh; /* window area geometry x, y, width, height, bar
excluded */
+static int mx[MAXMONITORS], my[MAXMONITORS], mw[MAXMONITORS],
mh[MAXMONITORS]; /* monitor area geometry x, y, width, height, bar excluded */
static unsigned int seltags = 0, sellt = 0;
static int (*xerrorxlib)(Display *, XErrorEvent *);
static unsigned int numlockmask = 0;
@@ -926,10 +931,14 @@
void
monocle(void) {
- Client *c;
+ int m, i;
+ Client *c = nexttiled(clients);
- for(c = nexttiled(clients); c; c = nexttiled(c-next))
- resize(c, wx, wy, ww - 2 * c-bw, wh - 2 * c-bw, resizehints);
+ for(m=0; mmons; m++) {
+ wx=mx[m]; wy=my[m]; ww=mw[m]; wh=mh[m];
+ for(i=((m==(mons-1))?-1:1); c i!=0; c = nexttiled(c-next),
i--)
+ resize(c, wx, wy, ww - 2 * c-bw, wh - 2 * c-bw,
resizehints);
+ }
}
void
@@ -1427,35 +1436,39 @@
void
tile(void) {
- int x, y, h, w, mw;
- unsigned int i, n;
+ int x, y, h, w, maw;
+ unsigned int i, n, r, g, m;
Client *c;
for(n = 0, c = nexttiled(clients); c; c = nexttiled(c-next), n++);
if(n == 0)
return;
- /* master */
c = nexttiled(clients);
- mw = mfact * ww;
- resize(c, wx, wy, (n == 1 ? ww : mw) - 2 * c-bw, wh - 2 * c-bw,
resizehints);
+ for(m=0, g=(n+(mons/2))/mons, r=n-g, n=g; c mmons; m++,
n=(rg?r:g), r-=n) {
+ wx=mx[m]; wy=my[m]; ww=mw[m]; wh=mh[m];
+ /* master */
+
Re: [dwm] dwm and dualhead
there should be a Bool usegrab in your config.h, check it against
config.def.h
Here's a slightly updated patch, the bar is drawn a little better now.
Jeremy
On Fri 12 Dec 2008 - 01:20PM, Johannes Wegener wrote:
thanks for your approach - but I was not able to compile it (patched
against dwm 5.3.1) it does not find the function usegrab (used in
movemouse and resizemouse...
On Thu, Dec 11, 2008 at 10:59:16PM -0500, Jeremy Jay wrote:
Here's my XRandR and multi-screen patch, its pretty much not what you've
asked for here, but I'll throw it out as a starting point. I haven't
had a chance to test it much, so don't yell at me if your screen
explodes...
one tag for all screens. status bar is only shown on screen 0 (although
this can very easily be set to another screen)
layouts updated for multi-head:
tile: windows are evenly divided among screens.
monocle: one window per screen, all remaining windows on last screen.
Jeremy
On Thu 11 Dec 2008 - 10:18AM, Mate Nagy wrote:
Hiho,
On Thu, Dec 11, 2008 at 09:39:19AM +0100, yy wrote:
on this list and, if somebody finds a great _general_ solution (which
seems difficult, but I would be love to be wrong), I'm sure Anselm
would be glad to include it in the official release.
Just my 2cts,
I don't see anything difficult about this. In fact, awesome generally
gets this right. This is what I want from dwm:
- handle each xrandr screen separately
including all data structures, so different layout, client set,
tagging, etc.
- draw statusbar everywhere (from the same input text)
- have a key-bindable function for:
- changing between screens
- move window to another screen
- do something semi-intelligent when a screen with clients goes away,
e.g. put clients in previous/next screen oslt.
Basically, it should behave as multiple separate dwms, except that
clients can be sent from screen to screen and all dwms have the same
configuration.
Speculation: in this configuration, especially when changing between
screens, moving the mouse pointer to the location of the focus might be
more important/desirable. This might be a compile-time option or patch..
Mate
diff -r 79bf47074a49 config.mk
--- a/config.mk Sat Dec 06 16:20:14 2008 +
+++ b/config.mk Thu Dec 11 22:50:24 2008 -0500
@@ -13,6 +13,8 @@
# Xinerama, un-comment if you want it
#XINERAMALIBS = -L${X11LIB} -lXinerama
#XINERAMAFLAGS = -DXINERAMA
+XINERAMALIBS = -L${X11LIB} -lXrandr
+XINERAMAFLAGS = -DXRANDR
# includes and libs
INCS = -I. -I/usr/include -I${X11INC}
diff -r 79bf47074a49 dwm.c
--- a/dwm.c Sat Dec 06 16:20:14 2008 +
+++ b/dwm.c Thu Dec 11 22:50:24 2008 -0500
@@ -42,6 +42,9 @@
#ifdef XINERAMA
#include X11/extensions/Xinerama.h
#endif
+#ifdef XRANDR
+#include X11/extensions/Xrandr.h
+#endif
/* macros */
#define BUTTONMASK (ButtonPressMask|ButtonReleaseMask)
@@ -52,6 +55,7 @@
#define MAX(a, b) ((a) (b) ? (a) : (b))
#define MIN(a, b) ((a) (b) ? (a) : (b))
#define MAXTAGLEN 16
+#define MAXMONITORS 8
#define MOUSEMASK (BUTTONMASK|PointerMotionMask)
#define WIDTH(x)((x)-w + 2 * (x)-bw)
#define HEIGHT(x) ((x)-h + 2 * (x)-bw)
@@ -206,10 +210,11 @@
/* variables */
static char stext[256];
-static int screen;
+static int screen, mons;
static int sx, sy, sw, sh; /* X display screen geometry x, y, width,
height */
static int by, bh, blw;/* bar geometry y, height and layout symbol
width */
static int wx, wy, ww, wh; /* window area geometry x, y, width, height,
bar excluded */
+static int mx[MAXMONITORS], my[MAXMONITORS], mw[MAXMONITORS],
mh[MAXMONITORS]; /* monitor area geometry x, y, width, height, bar excluded
*/
static unsigned int seltags = 0, sellt = 0;
static int (*xerrorxlib)(Display *, XErrorEvent *);
static unsigned int numlockmask = 0;
@@ -926,10 +931,14 @@
void
monocle(void) {
- Client *c;
+ int m, i;
+ Client *c = nexttiled(clients);
- for(c = nexttiled(clients); c; c = nexttiled(c-next))
- resize(c, wx, wy, ww - 2 * c-bw, wh - 2 * c-bw, resizehints);
+ for(m=0; mmons; m++) {
+ wx=mx[m]; wy=my[m]; ww=mw[m]; wh=mh[m];
+ for(i=((m==(mons-1))?-1:1); c i!=0; c = nexttiled(c-next),
i--)
+ resize(c, wx, wy, ww - 2 * c-bw, wh - 2 * c-bw,
resizehints);
+ }
}
void
@@ -1427,35 +1436,39 @@
void
tile(void) {
- int x, y, h, w, mw;
- unsigned int i, n;
+ int x, y, h, w, maw;
+ unsigned int i, n, r, g, m;
Client *c;
for(n = 0, c = nexttiled(clients); c; c = nexttiled(c-next), n++);
if(n == 0)
return;
- /* master */
c =
Re: [dwm] dwm on tablet pc
On Fri Dec 12, 2008 at 11:50:24AM +0100, jo...@freenet.de wrote: Has anyone tried to run dwm on a tablet pc and has a working patch set? patch set to do what? getting the buttons working was a bit of a voyage (all 12 mins of it) : http://blog.whats-your.name/post/2008/11/21/the-history-of-grass cheers
Re: [dwm] xprop patch
Anselm R Garbe dixit (2008-12-09, 19:44): If you consider that Neale's patch makes it upstream, what do you think about: while true do dwm done in .xinitrc to restart dwm? How do I exit back to xdm cleanly then? -- [a]
Re: [dwm] [slock] slock doesn't like to deactivate after password entry
On Tue, Dec 9, 2008 at 1:49 PM, Thayer Williams thay...@gmail.com wrote: On Tue, Dec 9, 2008 at 4:48 AM, Anselm R Garbe garb...@gmail.com wrote: 2008/12/9 Ali Gholami Rudi aliqr...@gmail.com: On Mon, Dec 08, 2008 at 04:00:48PM -0800, Thayer Williams wrote: I've been using slock for about two months now and, as per the subject, slock doesn't release my screen right away after a valid password entry. After inputing the password and pressing Enter, the screen remains blanked and no amount of input brings it up. I can actually see the LCD backlight flicking on and off with each subsequent keypress or mouse wiggle. I don't know how to handle others, but I use this patch for handling the flickering problem. AFAIK turning a lamp on and off excessively decreases its lifetime; that might be true for displays, too. Ali, thanks for that! This works great and I like the fact that I can customise the timeout values. It's too early to say for sure, but it also looks like your patch fixed my input issues (though I'm not sure how that could be). I've been using it for a few hours now and haven't encountered any problems yet. I just wanted to report that for whatever reason, Ali your patch does fix the slock unresponsiveness I mentioned in my initial post. Thanks again for that.
[dwm] plan for dwm
Hi, here is the plan: slock-1.1 will be released soon containing Ali's patch with some minor modifications. dwm-5.4 will also be released soon containing the transition patch with the proposed x property based status reporting, and Neale's spawn patch again, and possibly some other minor patches ;) After that 5.5 could contain a more advanced approach for multihead support (though I think I need to investigate further and experiment more into this direction, before agreeing on the final approach). It should also contain a cleaned up usage of the HEIGHT/WIDTH macros besides the reduction of the ugly 2 * c-bw occurrences throughout the code (I plan to move these border deductions to resize). Then there will be something else soon as well... Kind regards, --Anselm
Re: [dwm] plan for dwm
On Fri, Dec 12, 2008 at 07:15:55PM +, Anselm R Garbe wrote: Hi, here is the plan: slock-1.1 will be released soon containing Ali's patch with some minor modifications. dwm-5.4 will also be released soon containing the transition patch with the proposed x property based status reporting, and Neale's spawn patch again, and possibly some other minor patches ;) After that 5.5 could contain a more advanced approach for multihead support (though I think I need to investigate further and experiment more into this direction, before agreeing on the final approach). It should also contain a cleaned up usage of the HEIGHT/WIDTH macros besides the reduction of the ugly 2 * c-bw occurrences throughout the code (I plan to move these border deductions to resize). Then there will be something else soon as well... Kind regards, --Anselm I look forward to all the above mentioned changes, as well as this mystery item :) -- James Turner BSD Group Consulting http://www.bsdgroup.org
Re: [dwm] plan for dwm
On Fri, Dec 12, 2008 at 11:23 AM, James Turner ja...@bsdgroup.org wrote: On Fri, Dec 12, 2008 at 07:15:55PM +, Anselm R Garbe wrote: Hi, here is the plan: slock-1.1 will be released soon containing Ali's patch with some minor modifications. dwm-5.4 will also be released soon containing the transition patch with the proposed x property based status reporting, and Neale's spawn patch again, and possibly some other minor patches ;) After that 5.5 could contain a more advanced approach for multihead support (though I think I need to investigate further and experiment more into this direction, before agreeing on the final approach). It should also contain a cleaned up usage of the HEIGHT/WIDTH macros besides the reduction of the ugly 2 * c-bw occurrences throughout the code (I plan to move these border deductions to resize). Then there will be something else soon as well... Kind regards, --Anselm I look forward to all the above mentioned changes, as well as this mystery item :) Ditto. A big thanks to Anselm and everyone else contributing to these projects.
Re: [dwm] dwm on tablet pc
Try dwm-gtx. Onscreenkeyboards should work with it. :) Thanks for the hint. I tried your version of dwm, and cellwriter works. What is the essential part for this to work? Getting cw to work is the first step. I also tried the mouse actions for the bar, which are already implemented in dwm, but especially those with MODKEY do not work in conjunction with cw. There would still be much work to do regarding a clickable bar and of course a clickable version of dmenu for application launching. @yy: Emulating a 5 buttons mouse would only be possible by implementing onscreen buttons, I think, causing a similar amount of work. I am not a c programmer - writing a small patch is possible, but not more - I am more a script kiddie ;-) Atm I am using openbox and fbpanel, but I am missing dynamic tiling. Of course there are tile and whaw, but they are not sufficient for me. I will try to get it working with devilspie executing a perl script and issuing wmctrl. Kind regards, joten
Re: [dwm] plan for dwm
Hiho, On Fri, Dec 12, 2008 at 07:15:55PM +, Anselm R Garbe wrote: Hi, here is the plan: slock-1.1 will be released soon containing Ali's patch with some minor modifications. dwm-5.4 will also be released soon containing the transition patch with the proposed x property based status reporting, and Neale's spawn patch again, and possibly some other minor patches ;) After that 5.5 could contain a more advanced approach for multihead support (though I think I need to investigate further and experiment more into this direction, before agreeing on the final approach). It should also contain a cleaned up usage of the HEIGHT/WIDTH macros besides the reduction of the ugly 2 * c-bw occurrences throughout the code (I plan to move these border deductions to resize). Then there will be something else soon as well... Kind regards, --Anselm Just adding my support. I have described my views on the multihead issue, but any kind of real support will be really welcome. Dwm is still the best wm for me from all the choices.. Keep up the good work :) Mate
Re: [dwm] dwm-5.3
After taking some time and looking at the different signal headers on OpenBSD only #include sys/signal.h is required, no need to #include signal.h which contains additional functions. -- James Turner BSD Group Consulting http://www.bsdgroup.org
