> On May 26, 2016, 11:37 a.m., Matthew Dawson wrote:
> > While I appreciate the source of this change (I've almost never hit F1 
> > intending to open the doucmentation myself), I don't think a RR is the 
> > right place to discuss changes to our default shortcuts.  This takes a 
> > small survey of a small section of our community.  I think the VDG would 
> > probably be the best place to have a discussion about what help, if any, is 
> > triggered and on what shortcut (though if there is a better source I'm 
> > happy to take their input instead).  Once there is a consensus, then I'm 
> > happy to have those changes implemented.
> > 
> > Since there is a global way to disable F1 for people who find this annoying 
> > now, this is a -2 from me.  People annoyed at F1 can fix their issue now 
> > without code changes while we figure out the best plan forward.
> 
> Albert Astals Cid wrote:
>     The proper way of doing this is having metrics reporting that show how 
> quickly after pressing F1 you close khelpcenter, unfortunately the user 
> metric reporting got blocked on "this is spying our users", so now we don't 
> have any data that can back my claim that F1 as a shortcut is useless or 
> someone else's claim that it is vital.
>     
>     I will discard this and stop pursuing the idea, it's clear we're 
> stationary and people are scared of change or even getting the data to pursue 
> change.
> 
> Matthew Dawson wrote:
>     To be clear, I'm not against this change, I'm just against having the 
> conversation about this change in *this* communication channel.  Like I said, 
> if this is taken to something like VDG, and the consensus there is to remove 
> this shortcut, I'll happily take this (even if there are some objections).
>     
>     Please don't stop pursuing this!  I agree the current behaviour is 
> suboptimal and something new should be found.  My goal isn't to be stationary.
> 
> Albert Astals Cid wrote:
>     The kde-usability mailing list is subscribed here.  In my opinion that's 
> enough to get usability people to comment, your -2 means you think it is not.
>     
>     I do not have time to do more than what i have done, i have 29 okular 
> review requests pending and i should really get to review them this century, 
> so no, i'm not going to pursue this further.
>     
>     If you think the current behavior is suboptimal maybe you can be 
> convinced to do it ;)

I don't find RR are a great place for this type of conversation, especially 
something that may take a wider vision.  If kde-usability comes to a consensus, 
that's good enough for me.

Fair enough on your time constraints, I use okular all the time and appreciate 
your work in it :).  I'll see what I can do about it, though I have the same 
time problems.


- Matthew


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128019/#review95848
-----------------------------------------------------------


On May 26, 2016, 6:04 p.m., Albert Astals Cid wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/128019/
> -----------------------------------------------------------
> 
> (Updated May 26, 2016, 6:04 p.m.)
> 
> 
> Review request for KDE Frameworks and KDE Usability.
> 
> 
> Repository: kconfig
> 
> 
> Description
> -------
> 
> F1 is too important and too easy to trigger for something like Help, that be 
> honest you don't need a shortcut for (since you don't invoke Help that often).
> 
> 
> Diffs
> -----
> 
>   src/gui/kstandardshortcut.cpp 6be6309 
> 
> Diff: https://git.reviewboard.kde.org/r/128019/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Albert Astals Cid
> 
>

_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Reply via email to