Change Details

While I'm doing KCM rewrites, I experienced that we're loosing too much times because of 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. If we agree on that, someone can make a 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!

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. If we agree on that, someone can make a 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!

While I'm doing KCM rewrites, I experienced that we're loosing too much times because of 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. If we agree on that, someone can make a 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!