begin  quoting Paul Seelig as of Sun, Sep 01, 2013 at 01:54:42PM +0200:
[chop]
> 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).

I'd argue that this is not an _industry_ standard, only a _Microsoft_
standard. And if I wanted the Microsoft UX, I'd use Microsoft Windows,
thankyouverymuch.

I'd further argue that ^C/^V/^X are _not_ something the window manager
should touch without explicit user direction, because control-keys are
used by applications.  A window manager that intercepts, for example,
control-C will very quickly end up being deleted from any system I have
administrative access to or policy control over.

Now, extending the cut-buffer access beyond the universal *nix default 
of left-select right-extend middle-paste is not a bad thing -- so long
as it doesn't break standards that have been working well for decades
(I can't be the only one who wants to shoot developers who break ^S/^Q
for flow control?) unless the user explicitly sets it up that way.

I tend to use Mod4+<key> for window-manager shortcuts, and leave Control
for controlling the application.

> - Do not let WINGs based dialog boxes lose focus only after temporarily
> switching via alt-tab to another window and back again.

Right after no-focus-stealing is no-focus-forgetting, yes.

> - Enable full keyboard navigation of WINGs based applications, without
> the need to use any kind of mouse pointer.

As a touch-typist, I approve of this suggestion.

> 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.

Part of the reason I use WindowMaker is that it doesn't automatically ape
the bad user-experience that other systems and window managers do. I need
to get work done, not fight my system's "helpfulness". I keep ending up
with WindowMaker because it offers a reasonable level of eye candy without
sacrificing my ability to Get Stuff Done.

[snip]

TL;DR - "better" is not the same as "what everyone else is doing"

-- 
SJS


-- 
To unsubscribe, send mail to [email protected].

Reply via email to