Michael Stapelberg
2014-01-14 20:06:09 UTC
Hi Головин,
Thanks for your suggestion. I have CC'ed i3-discuss, where this should
have been sent to in the first place.
aware of that. Most usual users have no interest in using a tiling
window manager, and we have no interest in accomodating novice users.
useful :).
to improve mouse usage of i3.
reason it exists in the first place is because configs that are tailored
to your keyboard layout _have to_ be generated at runtime. The reason it
also offers you a choice between the alt and the windows key as a
modifier is that we strongly prefer the windows key (due to less clashes
with other applications), but not all laptops have it. Perhaps we can
drop it in a couple of years.
I hope I have explained well enough why I don’t think adding buttons is
a good idea, especially if it’s for catering to a group of users which
we explicitly don’t want to have at all. By focusing on power users, we
can make much better software for them, and the market for novice/light
users is already saturated with programs like GNOME, KDE, Xfce, LXDE and
others.
Thanks for your suggestion. I have CC'ed i3-discuss, where this should
have been sent to in the first place.
-----------
i3 buttons.
-----------
idea: add buttons to i3wm
This is not a problem. i3 is a niche window manager and we are veryi3 buttons.
-----------
idea: add buttons to i3wm
aware of that. Most usual users have no interest in using a tiling
window manager, and we have no interest in accomodating novice users.
- user cant see, how to mnipulate i3wm, he need to learn i3 hotkeys.
Which is good, because then she knows the hotkeys, and they are veryuseful :).
- i3wm need keybord for even simple things, like closing window, what
is not always userful.
Agreed. There is ticket #558 though, which is actively being worked on,is not always userful.
to improve mouse usage of i3.
- it can slow down users (launch applications is not so simple, and if program have a lot of hotkeys, like blender, user need to switch his mind form program to i3wm)
- Of course, user can remove all buutons, he can easily #comment it in config.
- add to i3wm first launch(where is win-alt choise) "show buttons",
default answer sloud be yes(! becase new user usualy just click
default, familiar have more attention and he easily choose)
We don’t want to make i3-config-wizard a configuration tool. The only- Of course, user can remove all buutons, he can easily #comment it in config.
- add to i3wm first launch(where is win-alt choise) "show buttons",
default answer sloud be yes(! becase new user usualy just click
default, familiar have more attention and he easily choose)
reason it exists in the first place is because configs that are tailored
to your keyboard layout _have to_ be generated at runtime. The reason it
also offers you a choice between the alt and the windows key as a
modifier is that we strongly prefer the windows key (due to less clashes
with other applications), but not all laptops have it. Perhaps we can
drop it in a couple of years.
just adding buttons to i3 can make avalibe this awesome tiling manager
for every user, you can get more donates!
I don’t need more donations.for every user, you can get more donates!
I hope I have explained well enough why I don’t think adding buttons is
a good idea, especially if it’s for catering to a group of users which
we explicitly don’t want to have at all. By focusing on power users, we
can make much better software for them, and the market for novice/light
users is already saturated with programs like GNOME, KDE, Xfce, LXDE and
others.
(it can be just xbm for begining, but png would be better)
(for example, xbm color is color of title text)
for example 'kill'
image is in ~/.i3
example: ~/.i3/close.xbm or ~/.i3/close.png
#button place image command
button left close.png kill
(First button on left side is first button with "left" in config, second is second...)
#here .png can be .xbm if you now want to make only .xbm
#close button on right
button right close.png kill
#full scree on the left
button left full.png fullscreen
#floating mode (simular to maximaze button)
button left floating toggle
#split in horizontal orientation
button left splith.png split h
you can do it, because you did system tray
launch buttons - reson, why i use gnome-panel, not i3bar
- left (from the left of workspace butons)
- right (from the right of tray)
- ?at center?
bar {
status_comand i3status
button right tabbed.png layout tabbed
button right splite.png layout toggle split
button left /usr/pixmaps/firefox.png exec firefox
}
(for example, xbm color is color of title text)
for example 'kill'
image is in ~/.i3
example: ~/.i3/close.xbm or ~/.i3/close.png
#button place image command
button left close.png kill
(First button on left side is first button with "left" in config, second is second...)
#here .png can be .xbm if you now want to make only .xbm
#close button on right
button right close.png kill
#full scree on the left
button left full.png fullscreen
#floating mode (simular to maximaze button)
button left floating toggle
#split in horizontal orientation
button left splith.png split h
you can do it, because you did system tray
launch buttons - reson, why i use gnome-panel, not i3bar
- left (from the left of workspace butons)
- right (from the right of tray)
- ?at center?
bar {
status_comand i3status
button right tabbed.png layout tabbed
button right splite.png layout toggle split
button left /usr/pixmaps/firefox.png exec firefox
}
--
Best regards,
Michael
Best regards,
Michael