On 08/29/2013 11:32 AM, Iain Patterson wrote: > Quoth I, > >> This patch allows wmaker to replace existing window managers with the >> --replace flag, like xfwm4 and metacity can. It also allows those >> window managers (or another wmaker) to replace wmaker in the same way. > >From a user's point of view, i think this is a very worthwhile feature.
Not only because it finally implements a feature that we already take for granted with various other window managers, but because it actually enhances on what wmaker already is. Thanks! If we want wmaker to really advance and stand up to current industry standards instead of just staying in the glorious past, then any feature additions like the --replace flag are the way to go. And while we are at it, there are some more feature enhancements which would be very worthwhile to be added, but which strangely enough nobody ever seems to have bothered about yet: - Enable copy'n'paste via industry standard ctrl-c/v keyboard shortcuts in the WINGs widget set, and enable exchange of clipboard selection and content also with any other standard widget set (e.g., gtk+/qt). - Do not let WINGs based dialog boxes lose focus only after temporarily switching via alt-tab to another window and back again. - Enable full keyboard navigation of WINGs based applications, without the need to use any kind of mouse pointer. I think these features are industry standards since loooong time and which are definitely missing in wmaker/WINGs. If people like us are mainly used to use wmaker like we are used to use it, we are probably missing the point of view of people who are used to other kinds of environments. In fact, lots of the people in my personal environment who tried out the wmlive distribution out of curiosity about what i was doing in my spare time, were rather turned off by the inability of wmaker to be managed without any mouse pointer. It actually took me a while to fully understand this, as i am so used to it that i considered it being normal. Bottom line is that this is not standard, but rather a severe shortcoming in usability. The other thing is that WINGs theming is severely limited, if not even simply broken when trying to integrate it with applications using other widget sets like gtk+ and qt. The latter can both be tricked to take on that NeXTish look (while offering at the same time the missing keyboard navigation features) and can even be tricked into accepting theming styles of each other (via gtk-qt-engine and various common themes). It is a pity that WINGs is so stuck with itself. So much room left for improvement, and so little capability on my behalf to do at least part of it myself. :( -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
