Thanks all for your kind reply! On Thu, 15 Sep 2011 09:44:44 +0200, Uli Schlachter wrote: > On 15.09.2011 09:14, Teika Kazura wrote: >> created a wiki page for it: >> http://sawfish.wikia.com/wiki/Comparison_of_extensible_window_managers > [...] > I tried editing your wiki, but the editor confuses me. Sorry.
Our hosting site (wikia) recently changed the editing interface, and if you ask me, it worsened. Sorry. I've done edit instead. I've just added one item "undo / history". Sawfish only rememebers the last operation, and undo is not provided. (Some users want it, I know, but I don't know if it's easy.) > [...] > So, is my understanding right and this counts as "repl"? Yep. :) > "Compositing": How come sawfish doesn't work with xcompmgr? I don't use compositing myself, and I don't know the status well. I'm going ask Sawfish community on this. In the past, I've done a couple of questionnaires on Sawfish usage, whose results are here: http://sawfish.wikia.com/wiki/Your_voice#How_do_you_use_Sawfish.3F The coming one will ask about composite, event synthesis, etc. Users often find such questions fun, and many wrote long answers. If Awesome community hasn't ever seen one, I recommend it. It's really amusing. > "XKB": Nope, xcb doesn't yet provide XKB bindings because it's > such an ugly protocol It's true, unfortunately (together with many many other X aspects), that xkb is a complete mess, but without xkb, you can't bind some keys. For example, a German user says ° (degree sign) is not available for actions. Anyway it's cumbersome to support xkb with Xlib, too. > "Input event synthesis": [...] For keyboard events one needs the > keycode which means that it becomes ugly with keyboard layouts etc > (26 is the keycode for 'e'). > $ echo 'for k, v in ipairs({"key_press", "key_release"}) do root.fake_input(v, > 26) end' | awesome-client > e # Hmm, you can bind keys, and I suppose they're specified like Alt + e # or so, *not* Alt + 26, so there must be easier way. If not, you can # easily change the core code to provide such function in the API. I use synthesis to emit mouse events with some key presses. For such simple purposes it's not necessary for window managers to support it, since there're many tools, though. (Unfortunately none of such tools are standard, and not so well maintained.) There's a notion similar to event synthesis, "event replay": you fetch an event, but allow that event get resent to the original target window. I use explicit replay against firefox; press of ctrl-l focuses the location bar, but for some reasons I also want the mouse pointer go there. So my Sawfish detects ctrl-l on firefox, move the cursor, and replay the key press. (I explicitly specify the coordinates, and I think it's inevitable.) > "Input translation per window": Hm, I never heard anyone asking for this. I don't use it either, but at least it's implemented by one, and another uses it now, so must be good for some. > but I'm unsure what kind of problems [input translation] could > cause... (E.g. what happens to the event's timestamp) In xlib, you can legally synthesize events, so I don't think timestamp can be a problem. (In Sawfish, you can't forge the timestamp, though.) > "Extra mouse features": [...] I'd like to ask how sawfish > implements [edge actions]. [...] Create 1px wide InputOnly windows > at the edge of the screen? [...] an InputOnly window couldn't be > done [in awesome] Bingo. Input-only window is easy to implement. Mouse polling maybe good, too. > "Large desktop": I guess this is the EWMH-kind of large desktop? The WM > internally implements one big screen and the workspaces just show different > parts of this? So that, e.g. when you move a window partially outside of a > workspace, it would show up on the workspace next to it. Yes. Large desktop is geometrical, and quite intuitive. Anyway you can implement a feature similar to large desktop with workspace = virtual desktop, but it's better to seperate both, at least to users, since both has each advantage. > If you want ideas for new columns, [...] > "Event sources for scripting (TODO: needs a better name)" > With awesome, you can register timers, react to button / keyboard events, have > your own code execute when some property changes (e.g. a window changes its > window title or some other code changes a window's position, a tag is renamed > etc) I guess it's common among "extensible window managers", and that's why I think they deserve a new, special notion "extenBlahBlah". (If a WM is not extensible / programmable, what you referred to is almost impossible.) I've added it to the wiki page and and Wikipedia page "X window manager" -> section "Window managers that are extensible" > we have some rudimentary dbus bindings (which are used to implement > the notification-spec, so e.g. "notify-send" and kde apps send their > notification to awesome) Thanks. Of course I knew awesome boasts dbus support, but I didn't write it since I don't know dbus well. ;) Now it settled. On Thu, 15 Sep 2011 08:34:41 +0000, "Robin H. Johnson" wrote: > 1. > Under screen comparison, I think it would useful to recognize the > possible combinations of virtual desktop and multiple monitors. > Specifically, one of the things that keeps on awesome, is that while I > have two monitors, the virtual desktops on each of them separately > controllable. A lot of other WMs enforce virtual desktop changing on all > monitors at once :-(. That's good, and it should be so. Sawfish is one of "other WMs". ;/ > 2. > Theming control: > [Wishes in Awesome] > > Robin Hugh Johnson > Gentoo Linux: Developer, Trustee & Infrastructure Lead I'm a Gentoo user for more than 6 years. Thanks a lot. On Thu, 15 Sep 2011 11:00:48 +0200, Dieter Plaetinck wrote: > Awesome does not support tabbing. [...] I see. Fixed the wiki. Teika (Teika kazura) -- To unsubscribe, send mail to [email protected].
