Arucard (Riaas Mokiem)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Sunday

  • Clear sailing ahead.

User Details

User Since
Apr 8 2016, 6:32 AM (415 w, 6 d)
Availability
Available

Recent Activity

May 5 2020

Arucard committed R985:20386962291f: Add a table-of-content to the Contribute page. (authored by Arucard).
Add a table-of-content to the Contribute page.
May 5 2020, 2:48 PM

May 4 2020

Arucard committed R985:e843972f2b77: Add a table-of-content to device types page. (authored by Arucard).
Add a table-of-content to device types page.
May 4 2020, 8:55 PM

Apr 14 2020

Arucard added a comment to D28554: Add Smart TV UX as device type.

Seems to be because I still had the "Differential Revision" field in the commit message:

Apr 14 2020, 7:02 AM · KDE Human Interface Guidelines

Apr 13 2020

Arucard added a comment to D28554: Add Smart TV UX as device type.

Thank you! You can formally Abandon this now.

Apr 13 2020, 5:47 PM · KDE Human Interface Guidelines

Apr 12 2020

Arucard added a comment to D28554: Add Smart TV UX as device type.

Created the merge request at https://invent.kde.org/websites/hig-kde-org/-/merge_requests/73

Apr 12 2020, 7:06 AM · KDE Human Interface Guidelines
Arucard added a comment to D28554: Add Smart TV UX as device type.

Sorry for responding so late as well. I'll re-submit according to the instructions you provided.

Apr 12 2020, 6:49 AM · KDE Human Interface Guidelines

Apr 4 2020

Arucard added a comment to D28554: Add Smart TV UX as device type.

As a side-note, I just wanted to mention that the Contribute section in the HIG doesn't actually explain how to submit the changes you make locally. I followed the instructions from this Community page. I'm not sure if this is correct and it actually took a bit of searching to find. So it might be useful to include up-to-date instructions on the Contribute page in the HIG, even if it's just a link to that same page (assuming that's the correct workflow to use).

Apr 4 2020, 12:06 PM · KDE Human Interface Guidelines
Arucard added a project to D28554: Add Smart TV UX as device type: KDE Human Interface Guidelines.
Apr 4 2020, 11:59 AM · KDE Human Interface Guidelines
Arucard added a reviewer for D28554: Add Smart TV UX as device type: KDE Human Interface Guidelines.
Apr 4 2020, 11:56 AM · KDE Human Interface Guidelines
Arucard requested review of D28554: Add Smart TV UX as device type.
Apr 4 2020, 11:54 AM · KDE Human Interface Guidelines

Oct 13 2018

Arucard added a comment to D15385: Improve convergence info and include device types.

So if it's okay with you, I'll accept the patch now, and after it's landed, I'll put on my liberal arts degree hat and submit another patch with proposed changes.

Sounds fair. I look forward to see what you make of it.

Oct 13 2018, 5:55 AM · KDE Human Interface Guidelines

Oct 8 2018

Arucard updated the diff for D15385: Improve convergence info and include device types.
  • Some more fixes based on feedback
Oct 8 2018, 5:28 AM · KDE Human Interface Guidelines
Arucard added a comment to D15385: Improve convergence info and include device types.

I removed the glossary now and changed the reference link to point to the new one. Can someone verify that it's correct? I'm not too familiar with Sphinx.

Oct 8 2018, 5:28 AM · KDE Human Interface Guidelines

Oct 7 2018

Arucard updated the diff for D15385: Improve convergence info and include device types.
  • More changes based on feedback
Oct 7 2018, 4:47 PM · KDE Human Interface Guidelines
Arucard added a comment to D15385: Improve convergence info and include device types.

I fixed most of what's mentioned in the feedback. I didn't quite agree that the user stories weren't relevant for Susan which I explained in the reply to those in-line comments.
Based on the feedback about the pointing device, I decided to also explain the benefit of having a keyboard. This could then replace the part about "traditional-style input" which was too vague anyway.

Oct 7 2018, 4:47 PM · KDE Human Interface Guidelines

Oct 6 2018

Arucard added a comment to D15385: Improve convergence info and include device types.

I fixed most of what's mentioned in the feedback.

  • I removed the netbook, smartwatch and tv device types.
  • I tried to rephrase everything to be more succinct. Let me know if this is sufficient.
  • I put manual line breaks at 80 characters
  • I created a separate Glossary page (which was still left from feedback by @fabianr)
  • I updated the screenshot with the new component names
Oct 6 2018, 11:37 AM · KDE Human Interface Guidelines
Arucard updated the diff for D15385: Improve convergence info and include device types.
  • Modified again according to further feedback
Oct 6 2018, 11:25 AM · KDE Human Interface Guidelines

Sep 23 2018

Arucard added a comment to D15385: Improve convergence info and include device types.

Thanks for reviewing. I've replied to some of the comments, and fixed the other ones.

Sep 23 2018, 12:05 PM · KDE Human Interface Guidelines
Arucard updated the diff for D15385: Improve convergence info and include device types.
  • Modified according to review feedback
Sep 23 2018, 12:04 PM · KDE Human Interface Guidelines

Sep 11 2018

Arucard added a comment to T7983: Reevaluate design vision and principles.

Even with "Solid" as design principle, I wouldn't say that this translates to translucency being off by default. Moving a window is inherently a transient state, so it might feel strange if we try to make this stable or rigid (in UI/UX terms).

Sep 11 2018, 6:11 AM · VDG, KDE Human Interface Guidelines

Sep 9 2018

Arucard added a reviewer for D15385: Improve convergence info and include device types: fabianr.
Sep 9 2018, 5:31 PM · KDE Human Interface Guidelines
Arucard requested review of D15385: Improve convergence info and include device types.
Sep 9 2018, 5:30 PM · KDE Human Interface Guidelines
Arucard added a comment to T7983: Reevaluate design vision and principles.

I agree that we shouldn't focus too much on specific guidelines (the micro direction) but I do think it helps us understand how these principles could be applied to such guidelines. That in turn should help define the principles in a way that they can correctly be applied to new guidelines later on. Especially since we're essentially working with a bottom-up approach, trying to extract the principles from the currently applied style, I do think a bit of micro discussion is unavoidable. But it's definitely good to keep the conversation on track.

Sep 9 2018, 10:06 AM · VDG, KDE Human Interface Guidelines

Sep 8 2018

Arucard added a comment to T7983: Reevaluate design vision and principles.

I would not consider the Breeze color palette https://hig.kde.org/style/color/default.html very subtle, but rather strong and vibrant.

Looking at the Breeze color palette, I think most of the colors are matte (which I think is a good thing). They aren't highly saturated colors, if that's the right term for it. But my reason for choosing "Subtle" as a design principle isn't just because the colors are somewhat matte. If you look at how they are applied, you usually see a single color (or very few main colors) which are decorated/highlighted with a few other colors. To me, this comes over as a very subtle use of color.

Sep 8 2018, 10:15 AM · VDG, KDE Human Interface Guidelines

Sep 7 2018

Arucard added a comment to T7983: Reevaluate design vision and principles.

However, that motto feels a lot like an operational motto. It is the way we "do" things rather than the way things "are", a more "procedural" approach rather than a visual one.

This was exactly why I didn't think this motto worked as design principle. Thanks for explaining it so clearly.

Sep 7 2018, 6:46 AM · VDG, KDE Human Interface Guidelines

Aug 29 2018

Arucard added a comment to T8146: Overall structure.

Maybe we should add a section about system integration, with information about how taskbar, launcher, system tray, ... should be used and what not to do.

I created a list of common (visual) components a while ago that may help with this. I tried to define what visual elements are usually available on any device, with a description of its intended functionality. This description is a bit abstract but I also provide more concrete descriptions of what exactly is used for each component on a specific device type.

Aug 29 2018, 10:49 AM · KDE Human Interface Guidelines
Arucard added a comment to T7983: Reevaluate design vision and principles.

TL;DR I think the KDE HIG needs to use a unifying concept as its main principle. This is likely to be vague but you can explain how it relates to the HIG. An example of such a unifying concept is kirigami (the art of folding and cutting).

Aug 29 2018, 10:25 AM · VDG, KDE Human Interface Guidelines

Jun 1 2018

Arucard added a comment to T2175: Convergence of Plasma shell.

A while ago, I did some research on how convergence might work. I ended up with an overview of possible device types and a description of the corresponding user experience. I also tried to identify common elements in the UI that would need to be converted in order to move from one device's UX to another. I've documented this on the community wiki:
https://community.kde.org/Plasma/Convergence_Overview
I also created a forum topic for feedback, which you can find here:
https://forum.kde.org/viewtopic.php?f=285&t=131170

Jun 1 2018, 6:01 AM · Plasma, Plasma: Mobile