The WMFS Thread (Window Manager From Scratch)

sironitomas · 2011-02-26 04:22:07

anonymous_user wrote:

I had set_client_master set to false however changing it to true had no effect on the issue.

I can confirm, I also have this issue.

And goiing full-screen with the max layout is kind of messy.

Anyway, your work is great.

Regards!

Last edited by sironitomas (2011-03-03 15:01:53)

Replika · 2011-03-09 05:11:19

Hi, I've just switched from dwm/awesome to wmfs.
- How can I set selected client to master?
- Is there a way to make new clients attach above selected client?

thechitowncubs · 2011-03-11 04:47:51

Replika wrote:

Hi, I've just switched from dwm/awesome to wmfs.
- How can I set selected client to master?
- Is there a way to make new clients attach above selected client?

Alt + t

Don't know what you mean about the 2nd question

Replika · 2011-03-11 11:09:49

thechitowncubs wrote:

Alt + t
Don't know what you mean about the 2nd question

Thanks for your answer.
1. I mean to set directly current selected client as master, not to swap with the next one.
Same as Modkey+Return in dwm or Modkey+Ctrl+Return in awesome
2. http://dwm.suckless.org/patches/attachabove
The new client is placed right above selected client. Any hints to hack the code?

bacardi55 · 2011-03-11 13:39:57

Replika wrote:

thechitowncubs wrote:
Alt + t
Don't know what you mean about the 2nd question
Thanks for your answer.
1. I mean to set directly current selected client as master, not to swap with the next one.
Same as Modkey+Return in dwm or Modkey+Ctrl+Return in awesome
2. http://dwm.suckless.org/patches/attachabove
The new client is placed right above selected client. Any hints to hack the code?

"attachabove makes new clients attach above the selected client (instead of always becoming the new master)"
If I understand correctly, you want to open a new client as a master or not, you have to see the
set_new_win_master = true / false
in the client part of the wmfsrc

Replika · 2011-03-12 04:24:31

Hi,

bacardi55 wrote:

If I understand correctly, you want to open a new client as a master or not, you have to see the
set_new_win_master = true / false
in the client part of the wmfsrc

Here is how it works:
(*) indicates that the window is currently selected (focused)

|        |  2  |
|        |-----|
|   1    |  3  |
|        |-----|  <-- New window will be inserted here
|        |  4* |

                  <-- New window will be inserted on the top.
|        |  2* |    This case is same to wmfs' behavior when  
|        |-----|    "set_new_win_master = false"
|   1    |  3  |
|        |-----|
|        |  4  |

|        |  2  |         |        |  1  |
|        |-----|         |        |-----|
|   1*   |  3  |  -->    |   5    |  2  |
|        |-----|         |        |-----|
|        |  4  |         |        |  3  |
                         |        |-----|
                         |        |  4  |
This case is same to "set_new_win_master = true"

This helps me to control the order of related windows as well as set the new window to master or not.

Also about the question 1, I mean if i am working in window 3, and want to move it to the master area with only one hotkey, not have to swap 2 times with the window 2 and 1.

phoneymonkey · 2011-03-13 19:05:22

Hi, I just started using WMFS.

I'm trying to get irssi to open up in tag 4. I made a rule for it and set it to tag 4. However, when I type irssi in any urxvt window, it'll open there (regardless of tags) instead of going into tag 4.

So I thought of a little workaround to that by aliasing urssi="urxvt -e irssi" and changing the instance and class to "urssi", but it didn't work as I expected.

Any tips?

Last edited by phoneymonkey (2011-03-13 19:05:41)

jasonwryan · 2011-03-13 19:35:38

You will need instance and class for terminal applications:

 
Rule:
[rule] instance = "irssi"         class = "irssi"         screen = 0     tag = "3"  max =  "true"  [/rule]
Key:
[key] mod = {"Control", "Alt"} key = "i" func = "spawn" cmd = "urxvtc -name irssi -e irssi" [/key]

shibo · 2011-03-14 01:24:36

hey everyone!
i tried dozens of wms, and now i finally found the one perfect for me!
i simply love the way it works for me and with me. but i still have a question:
while playing around with the different wms i had compiz running for a short while. overall i hated it, but it still had this handy expose feature (by a simple keybinding it showed an overview of all running clients on all workspaces). i was wondering if the config for wmfs holds some settings to imitate this function? i have a keybinding cloned 9 times which calls tag_toggle_additional for every tag. this at least shows me every running client from all tags. but when i change the focus to a client which is not on the currently active tag, the tag is not changend. so when pressing the keybinding again, everything just returns back to how it was before. it would be great if the tag would have changed to the one holding the last focused client.
so is there a setting which does this exact thing?
it's not of great importance for me, but i still wanted to know

oh and something quite off topic to my question:
i found the opacity setting is working with a running xcompmgr, but i kind off disliked the focused client beeing fully visible. even though i have no programming skills, i searched opacity with grep in the sources, was pretty sure the client.c is the file where the magic is done, and changed it a bit. in client_focus(Client *c) i copied the XChangeProperty function, pasted it right under the XDeleteProperty function and changed the sel->frame to c->frame. that made the focused client transparent as well. and since one of the arguments is (uchar *)&conf.opacity, i took what i found in config.c and adopted it to client.c. now i have an additional line above and below the new XChangeProperty saying conf.opacity = 200 << 24; and conf.opacity = 150 << 24;.
and this actually works, but i don't really know why and how and.... i was just lucky
so i was wondering: is someone around here who tweaked the same thing, but maybe more.. erm.. elegant/correct/less quick-and-dirty-hackish? or maybe even a patch that gives the wmfsrc an additional setting to change the focused clients opacity seperately?

p.s.: i'm very sorry for my poor english and my bad writing style. i suck at languages, even my mother tongue..

shibo · 2011-03-16 11:39:46

hi again!
i've managed to solve my "problems".
here's what i've done:

opacity:
- structs.h: under "uint opacity" i added
```
uint opacityfocus
```
- config.c: in the conf_misc_section i cloned every opacity entry and changed it to:
```
uint opacityfocus = 255;
```
```
opacityfocus           = fetch_opt_first(sec, "255", "opacityfocus").num;
```
```
if(opacityfocus > 255)
    opacityfocus = 255;
conf.opacityfocus = opacityfocus << 24;
```
- client.c: in the function client_focus i commented out the XDeleteProperty function, copied the XChangeProperty function and pasted it under the XDeleteProperty function. then i changed it like this:
```
XChangeProperty(dpy, c->frame, net_atom[net_wm_window_opacity], XA_CARDINAL,
                      32, PropModeReplace, (uchar *)&conf.opacityfocus, 1);
```
- the wmfsrc now has the additional setting opacityfocus, which is the opacity for the focused window

expose:

config.c: i added to the function list:

{"tag_toggle_expose", uicb_tag_toggle_expose },

wmfs.h: under tag.c i added:
```
void uicb_tag_toggle_expose(uicb_t);
```

client.c: in the function ishide i changed the if statement to this:

if(((c->tag == (uint)seltag[screen] || c->tag == MAXTAG + 1) && c->screen == screen)
               || tags[screen][seltag[screen]].tagad & TagFlag(c->tag) || (uint)seltag[screen] == 9 )

(by this tag 9 is unusable for me, except for the expose feature. which i'm perfectly okay with)

tag.c: i added this function:

void
uicb_tag_toggle_expose(uicb_t cmd)
{
    (void)cmd;

    int i;

    screen_get_sel();

    if((uint)seltag[selscreen] == 9)
    {
        tag_set(sel->tag);
        arrange(selscreen, True);
    }
    else
    {
        tag_set(9);
        arrange(selscreen, True);
    }

    for(i = 1; i < conf.ntag[selscreen] + 1; ++i)
        tags[selscreen][i].request_update = True;

    return;
}

i added the keybinding super + e to the func tag_toggle_expose.

espacially the expose thing is very ugly, but seems to work (in the first tests at least). this is how it's done now:
all clients are displayed on the tag they're assigned to, plus on tag 9 (the changed ishide function does this). the new tag_toggle_expose function just changes to tag 9 if the currently active tag is not 9, and if it is 9, it changes to the tag the currently focused client is assigned to. so now when in doubt where to find a client, i just press super + e, get an "overview" of all opened clients, focus the one i was looking for, press super + e again... and there i am, on the tag the client belongs to, with the focus on the client. pretty handy from time to time
btw.: i managed this without any programming skills just by browsing, copying und changing the sources. all thanks to the good comments and naming of the functions and variables. so this is not intended to be good code in any way! i don't even really know why it's working, it just does... somehow

greetings

Last edited by shibo (2011-03-16 12:14:19)

bacardi55 · 2011-03-16 12:57:36

can you make a "real" patch of these changes and submit a patch in a feature request please ?

It would be easier for one of the dev to analyse it (and possibly merge it)

shibo · 2011-03-16 14:48:52

i'm sorry what i've done already got very more complicated than i imagined.
i just wrote it down in case that someone would be interested.

but of course i can write a patch containing what i've done (even though i would have done it completly different if i would know how to program) and write a feature request. is diff used for something like that? sorry i never wrote any patches...

anyway, is expose a feature anyone would like to have? i'm asking because i just know of 2 wms implementing this feature (technicaly awesome doesn't implement it either, but there's a lua plugin for it adding this functionality).

bacardi55 · 2011-03-16 16:23:58

to make a feature, just git diff > patch is enough

This feature can be usefull for some user too. We will check your diff and we may apply it (with ou without changes).
I ask for a diff for 2 reasons :
- xorg62, the main dev, don't come around here
- A diff is easier to analyse than juste a post on a forum

:-)

thanks anyway

shibo · 2011-03-16 17:50:10

okay done.

thanks!

The_infinite_loop · 2011-03-17 06:12:31

Yes sir, I'd like that expose feature to try. Now I'm not quite dependent of expose as I was a while back when I used Mac OS and Ubuntu, but if you can implement it then I think it's ok to have it as an option.

bacardi55 · 2011-03-17 14:15:02

shibo wrote:

okay done.
thanks!

Thanks,

I'm actually working on your "expose" feature.
I can't use your diff though, i won't do it the way you did.

Wait for it a little longer

shibo · 2011-03-23 17:19:23

bacardi55 wrote:

I'm actually working on your "expose" feature.
I can't use your diff though, i won't do it the way you did.
Wait for it a little longer

sorry i haven't been around here for a few days, i'm right in the middle of my last exams for this semester.
i just downloaded your branch and tried the expose feature. thank you very much!

i'll keep using it, it works just perfectly!

bacardi55 · 2011-03-23 17:55:15

shibo wrote:

bacardi55 wrote:
I'm actually working on your "expose" feature.
I can't use your diff though, i won't do it the way you did.
Wait for it a little longer
sorry i haven't been around here for a few days, i'm right in the middle of my last exams for this semester.
i just downloaded your branch and tried the expose feature. thank you very much!
i'll keep using it, it works just perfectly!

Be carefull, I just made some fix couple hours ago
glad you like it ! Now, we just have to wait for xorg62 to merge it in the master tree…
Meanwhile, there is a couple of feature like this one that are only on my branch, so enjoy :-)

ggarm · 2011-04-06 23:22:30

A welcomed feature would be the option of setting an application size.
For instance in the rules section one could have a free_width & free_height parameters.

In that way one could specify the size an application would have in a free layout.
Or even an option to always start an application at given position (for example, with variables, start_x & start_y).

Either of those features would be greatly appreciated

bacardi55 · 2011-04-08 08:31:44

ggarm wrote:

A welcomed feature would be the option of setting an application size.
For instance in the rules section one could have a free_width & free_height parameters.
In that way one could specify the size an application would have in a free layout.
Or even an option to always start an application at given position (for example, with variables, start_x & start_y).
Either of those features would be greatly appreciated

For all feature requet, the best way is to post on the redmine (wmfs.info).
I think I'm the only dev of wmfs that comes on this topic…
This feature is a good idea and isn't that hard to dev, so create a feature request

ggarm · 2011-04-08 08:53:07

bacardi55 wrote:

For all feature requet, the best way is to post on the redmine (wmfs.info).

Okay, request added

sironitomas · 2011-04-08 18:02:24

bacardi55 wrote:

I think I'm the only dev of wmfs that comes on this topic…

Maybe because Arch users are the ones who most support this WM?

jonyamo · 2011-04-16 03:14:17

I'm fairly new to tiling window managers, recently converted from Xfce, and so far I absolutely love wmfs. With that being said I have two questions (although they are somewhat related):

1. I generally use the max layout and find titlebars just take up unnecessary space, so I have them set at 1px, however, I have one tag set to a free layout where I can open apps such as gimp. The problem is since all my titlebars are basically non-existent I can't move any clients around in the free layout. Am I missing something or without being able to click on a titlebar is it impossible to move clients around?

2. I ran into an issue running firefox without a titlebar. I clicked on a link at a particular site that opened a new window, without a titlebar I didn't have access to a close button and therefore was stuck, unable to close the new window. I have firefox set to open my tabs and windows from last time so every time I restarted firefox that window was still hanging around. So, is there a way to toggle titlebars on and off... or perhaps a way to kill windows without killing the whole client... or some other answer I'm not thinking of?

I realize I could just suck it up and actually use titlebars but I'd rather avoid that if possible.

Thanks in advance.

anonymous_user · 2011-04-16 03:29:46

1. Use the modifier key (default is Alt) and press the left mouse to move windows.

2. At least for me, the default keybind for client_kill only kills the current window not the entire client. Just try it (Alt-q).

jonyamo · 2011-04-16 19:48:30

anonymous_user wrote:

1. Use the modifier key (default is Alt) and press the left mouse to move windows.
2. At least for me, the default keybind for client_kill only kills the current window not the entire client. Just try it (Alt-q).

Thanks, both worked perfectly. I thought I had already tried client_kill and it killed the entire browser, but apparently not. Thanks again.

Arch Linux

#126 2011-02-26 04:22:07

Re: The WMFS Thread (Window Manager From Scratch)

#127 2011-03-09 05:11:19

Re: The WMFS Thread (Window Manager From Scratch)

#128 2011-03-11 04:47:51

Re: The WMFS Thread (Window Manager From Scratch)

#129 2011-03-11 11:09:49

Re: The WMFS Thread (Window Manager From Scratch)

#130 2011-03-11 13:39:57

Re: The WMFS Thread (Window Manager From Scratch)

#131 2011-03-12 04:24:31

Re: The WMFS Thread (Window Manager From Scratch)

#132 2011-03-13 19:05:22

Re: The WMFS Thread (Window Manager From Scratch)

#133 2011-03-13 19:35:38

Re: The WMFS Thread (Window Manager From Scratch)

#134 2011-03-14 01:24:36

Re: The WMFS Thread (Window Manager From Scratch)

#135 2011-03-16 11:39:46

Re: The WMFS Thread (Window Manager From Scratch)

#136 2011-03-16 12:57:36

Re: The WMFS Thread (Window Manager From Scratch)

#137 2011-03-16 14:48:52

Re: The WMFS Thread (Window Manager From Scratch)

#138 2011-03-16 16:23:58

Re: The WMFS Thread (Window Manager From Scratch)

#139 2011-03-16 17:50:10

Re: The WMFS Thread (Window Manager From Scratch)

#140 2011-03-17 06:12:31

Re: The WMFS Thread (Window Manager From Scratch)

#141 2011-03-17 14:15:02

Re: The WMFS Thread (Window Manager From Scratch)

#142 2011-03-23 17:19:23

Re: The WMFS Thread (Window Manager From Scratch)

#143 2011-03-23 17:55:15

Re: The WMFS Thread (Window Manager From Scratch)

#144 2011-04-06 23:22:30

Re: The WMFS Thread (Window Manager From Scratch)

#145 2011-04-08 08:31:44

Re: The WMFS Thread (Window Manager From Scratch)

#146 2011-04-08 08:53:07

Re: The WMFS Thread (Window Manager From Scratch)

#147 2011-04-08 18:02:24

Re: The WMFS Thread (Window Manager From Scratch)

#148 2011-04-16 03:14:17

Re: The WMFS Thread (Window Manager From Scratch)

#149 2011-04-16 03:29:46

Re: The WMFS Thread (Window Manager From Scratch)

#150 2011-04-16 19:48:30

Re: The WMFS Thread (Window Manager From Scratch)

Board footer