System Settings KCM Tidying

[Jan Grulich]

Hi,

I added myself to "Connection" KCM if you don't mind, but I have a question. 
Do you expect that all KCMs will be completely rewritten in QML? I'm just 
afraid that rewriting the editor part into QML will be more than a long 
process. There is so many kind of connections, not even mentioning VPNs, with 
tons of possible properties. If you do expect it to be completely written in 
QML, we will have to probably find some compromise or give it more time. If 
the editor part can still be QWidget based, then according to the mockup it 
shouldn't really be a problem to change it as the code base is quite ready for 
that.

Regards,
Jan

On pondělí 23. října 2017 11:10:41 CEST David Edmundson wrote:
> Andres Betts has done a fantastic job of a tonne of doing an initial mockup
> of the new KCMs.
> 
> The mockups are available here:
> https://phabricator.kde.org/M112
> 
> This is going to be a combination of UI redesign, code cleanup and QtQuick
> porting.
> 
> We have a workboard to track them all redesigns/porting here:
> https://phabricator.kde.org/project/view/254/
> 
> If you want to work on a KCM, we should split into a new pholio review for
> that KCM, discuss details, and add a link (edit related objects) in the
> pholio to the task in the workboard. Llike here:
> https://phabricator.kde.org/M111
> 
> Please ignore the new sidebar for now.
> 
> It's a good opportunity for anyone to get involved, just assign the task to
> yourself.
> 
> I think most of these need a bit of back and forth before even starting
> coding.
> Possibly even working mockups.
> 
> I want to see things done properly per KCM so that they last the next 15
> years; Any new KCM should have working i18n, a10y, RTL, keybaord nav and be
> super super tested, before merging.
> 
> As 5.12 is LTS, lets not treat the workboard as a race, there is a branch
> in plasma-desktop called KcmQmlPorts that is worth making use of.