KCM Template in QML
Open, HighPublic

Description

While I'm doing KCM rewrites, I experienced that we're loosing too much time on small issues which are not small when they come all together. These issues come out dynamically so the development time takes more time than it should. More important than that, the backend(qml)+frontend(what user see) quality, consistency decreases significantly.

So how to solve the problem ? I think we should have some coding standarts for KCMs. How ? We should have a KCM Template written in QML (with Kirigami) that consists of all the basic QtControls inside it and other KCMs should be done according to template. HIG, Kirigami, VDG teams should agree on the template so developers can only focus on the template.

How to make this KCM Template happen ? Someone experienced can make a step-by-step plan for that. At least 1 person from related teams (HIG, Kirigami, VDG) and developers can take part in plan implementation.

After the template, KCM rewrites will be faster and more consistent so frontend+backend quality will increase significantly. I can support my thesis with lots of real-life examples that I have experienced.

Actually this task will be more than a Template. This task will make the bones stronger between HIG, VDG and Kirigami teams.
HIG : Standarts
VDG : Mockups
Kirigami : Best way to implement them
Stronger Bones : Quality work!

furkantokac triaged this task as High priority.
furkantokac updated the task description. (Show Details)Jun 10 2018, 8:55 AM
furkantokac updated the task description. (Show Details)Jun 10 2018, 9:03 AM

Let me know if I can help with anything

fabianr added a subscriber: fabianr.EditedJun 11 2018, 7:38 AM

These are probably the most relevant existing HIG pages:

There is a open Phab review D12961 for the first two pages ongoing.

There is the plan to alter the pages about Alignment and Metrics, placement & keylines to be more general and focus less on forms and add instead a content pattern for forms. In my opinion the content pattern about forms would be a pretty good place for the HIG concerning results of this task.

Let me know if I can help with anything

These are probably the most relevant existing HIG pages:

Thanks guys. I'll start working on this. I'll share the Phab Patch page in here. You can keep your suggestions from there too.

Here is a first mockup that can help!

Visually, I'm not a huge fan of how those sub-labels and sub-fields break the alignment pattern. What's the application for them? Are they even needed at all?

Visually, I'm not a huge fan of how those sub-labels and sub-fields break the alignment pattern. What's the application for them? Are they even needed at all?

My first choice is to keep them aligned as well. I am just thinking ahead for an option where we don't have direction.

GB_2 added a subscriber: GB_2.Jan 6 2019, 8:57 PM