- User Since
- Sep 15 2015, 6:32 PM (195 w, 4 d)
Feb 7 2019
Dec 27 2018
Nov 27 2018
Integrating it in one page is definitely an improvement!
Some detailed comments (I am aware that those things introduced with this layout change, they just become apparent now):
- "About" at the top of the page and "About Discover..." are redundant. I'd recommend just integrating the Copyright and license lines above the hline and removing the "About Discover..." heading
- "Libraries" -> "Libraries used" (might be a bit too long for a tab title but as a title on a page it's perfectly fine)
- I'd maybe remove the "Please use..." line above the authors because we have the "Report Bug..." button at the top anyway so it would be redundant. If you fear that users might miss the button up there, I'd opt for moving the button elsewhere rather than having two different places for bug reporting on the same page
Oct 30 2018
Great work thank you!
Suggestion for one wording change below, but I'll accept the revision already since it's a small change
Oct 14 2018
Read to land from my perspective, now, thank you again for your work!
And sorry for taking so long to review, I had forgotten that my inaction was blocking the whole process.
Oct 7 2018
Thank you for the changes and replies. The changes are good, now all that's left from my perspective is finding a better word for what you call "configuration", because when especially KDE people read "configuration", they think about something entirely different from what you mean here.
Thank you for this very detailed and comprehensive write-up!
I have a few comments on specific parts, but with these fixed, I believe it's ready to land.
Aug 30 2018
@helderc Yes, we still do mentorship programs!
We regularly participate as a mentoring organization in Google Summer of Code, and we have our own mentoring program called Season of KDE ( https://season.kde.org ).
Apart from that, I'm sure the Kile team qill alo be happy to help if you jump on their mailing list.
I only have a few language-related comment, I fully agree with the content.
Aug 2 2018
Jul 31 2018
Jul 23 2018
Only one suggested rephrasing and one small typo fix (see inline comments).
Jul 15 2018
So, first (and perhaps for me only one this time) guerilla test:
- Plasma user for several years (because I recommended it to her)
- Frequent but generally mostly "non-technical" computer user
- Uses Plasma in English but isn't a native English speaker
- Has quite some experience with GIMP (also in English) and Snapseed, but not with a professional background or education
Jul 13 2018
The Unify Outputs button definitely makes sense to be there, but I'm not sure about the "Scale display" button.
I know that doing user research is not something favored here, but given how easy it is to use some user testing to settle discussions like this in a fact-based manner, I would really suggest the following:
Each of us here who knows people that use English as their UI languague (regardless of whether they are native speakers or not, doesn't matter if they use Plasma) takes a couple of them,
- shows them the screenshots with both terms (individually, in randomized order)
- asks them what they think this setting means
- records the answers
- records whether the participant should be considered a "regular" or "advanced" users
Jun 27 2018
We have organized some of the above trainings for Akademy!
Please find the trainings at https://community.kde.org/Akademy/2018#Trainings and add your name to the linked page if you want to participate!
Jun 4 2018
May 16 2018
More concrete suggestion: Move the Dolphin screenshot to the top, next to the mobile screenshot.
Currently we have a screenshot of the nouseover in Dolphin in here, but screenshots for swipeListItem only in the corresponding page. That gives preference to the Dolphin pattern because lazy people will implement what they see first. Therefore there should either be screenshots for both options here, or no screenshots at all.
May 4 2018
See inline comments. Otherwise it looks good!
May 3 2018
Apr 29 2018
The league of professional system administrators has a code of ethics: https://lopsa.org/CodeOfEthics
Apr 5 2018
- So do we have context menus in Kirigami / QQC2 right now or not?
- And what about spin boxes? Is there actually a QQC2 for those? Apart from that technical question: I would not recommend them on mobile, their buttons are too small for touch.
- Is there a traditional tooltip in QQC2?
- Last time I talked to people, there was no treeview in QQC2. Is there one now?
Mar 22 2018
- Drawers are not mobile-only. Most desktop apps will probably opt for sidebars instead of drawers on desktop, but if you want to allow users to show some UI elements only on demand, a drawer can make sense even on desktop. They just work slightly differently (on desktop the drawer stays open until you close it manually), but that should be described within the page. It's still the same pattern
- As far as I know, Kirigami does not have a menubar and so far doesn't plan to have one, so that would be QWidget-only
- Plasma does have context menus
- Currently Kirigami uses toolbars only on desktop (on mobile they are floating action buttons). This might change in the future, but for the time being, toolbars are desktop-only
Feb 26 2018
light weight -> lightweight
look in reStructuredText like this -> looks like this in reStructured Text
Feb 21 2018
Now it has the same icon as the handle for the Context Drawer. On the one hand that's good because they do very similar things, but on the other hand if an app uses both, it could be a bit confusing
Feb 9 2018
Feb 6 2018
Jan 19 2018
This is a clear improvement from my perspective, and I don't see it introducing any usability issues.
I think that when at the bottom, having the combobox is okay because it's not too prominent. The only problem I see is that it means that changing a combobox changes the content above it, which is not usually expected behavior for a combobox.
Jan 14 2018
Dunno why I only noticed it now, but of course then this is not the right place to fix it. Sorry for the noise.
My only concern would be that in the mouseover state the contrast between the grip and groove is quite low. This could make the two difficult to distinguish, especially for color blind users. Could perhaps the contrast in terms of brightness be increased a bit?
Dec 30 2017
This layout makes more sense to me as well overall. The only thing that I find a bit strange is that the summary now looks a bit like a headline, especially given that the application name is in the toolbar instead of the content area. I'm wondering if we should move the name and icon into the content area.
Dec 21 2017
Dec 20 2017
With that many available algorithms, the combobox solution makes more sense to me as well.
@James In fact, this is exactly what we've promised people in 2014 ( https://sessellift.wordpress.com/2014/04/02/choose-your-own-experience-this-time-its-for-real/ ), and what we've been getting the technology ready for since then.
The Plasma team is against shipping the other L&Fs directly with Plasma because that would mean they'd have to maintain them in case the original author loses interest, but getting them with a one-click install via store.kde.org is the idea.
Nov 29 2017
This proposal unfortunately was not selected as a goal for KDE as a whole to focus on.
That does not mean that we should not work on it, of course. As the discussion here shows, there is a relevant subset of the community who is interested in this topic, and I think we should work on it anyway, even if the whole of KDE is not focusing on it.
These are two different things, and both relevant. Yes, things should work "out of the box". Yes, things should ideally be self-explanatory.
Games (regardless of platform) and many mobile apps and OSes have shown, however, that it's often not possible for everything to be self-explanatory. Or if you make it so, you end up with a "chatty UI" that annoys users once they've figured it out.
Nov 28 2017
Nov 22 2017
Nov 18 2017
I can confirm that the dropdowns work on mobile now, thanks for fixing this!
Nov 14 2017
Nov 12 2017
Why don't we do this the way Firefox does it: Have a menu entry that puts the whole UI in config mode.
That works far better then trying to make each individual config feature discoverable.
Nov 6 2017
much better version control. eg at the moment it's next to impossible to create and discuss a draft
Nov 3 2017
Oct 20 2017
Oct 18 2017
So, what do we do with this proposal and https://phabricator.kde.org/T7116 now? They are so similar that it really makes little sense from my perspective to keep them separated.
Can @ngraham and @neofytosk maybe see how to proceed with merging them into one which contains all aspects of both?
Otherwise votes would end up split between the two, effectively reducing the chance for either of them to be selected.
Oct 15 2017
@laysrodrigues Yes, that is exactly what this proposal is about :)
Inlcude reminder of duty to attend AGM or find proxy
@hook We saw you subsrcibed to this task. Would you be interested in looking into this? That would help us a lot!
Oct 14 2017
I am definitely all for getting design more involved, but I feel that this proposal needs to be more detailed and concrete before I'm ready to sign it.
Oct 9 2017
I'm happy that there is a lot of discussion happening here, but maybe the discussion about annotations in Okular is getting a bit too much into detail for this point in the process.
So let's maybe summarize it for now as "There are potentially some issues with compatibility of Okular annotations, so if this goal gets selected, this could be one of the things we look into, together with academic / research users.
Oct 6 2017
Oct 5 2017
This is hugely important, from an accessibility, internationalization as well as usability perspective. That's why I'd be happy to help with UX design and testing.
Oct 4 2017
Oct 3 2017
Oct 2 2017
Colors are more @jensreuterberg 's thing.
Sep 25 2017
This is a goal which (hopefully) pretty much everyone in KDE can rally behind (otherwise our Vision, Mission and Strategy would not reflect the community's).
Sep 21 2017
Yes, I totally agree.
Application Dashboard in Plasma initially shows recent applications by default (which makes a ton of sense!).
Don't worry: After many years working as a usability consultant and UX designer, I know that I have to distinguish between my own needs and user needs.
Sep 13 2017
Why don't we simply copy the Firefox dialog?
Firefox has a big userbase and with the default settings, the vast majority of users will see this dialog at some point. Therefore if their wording was problematic, it's very likely someone would have flamed them for it.
So I'd consider their dialog "real-world tested".