[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: System settings KCM redesign
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2017-07-31 14:33:01
Message-ID: CAGeFrHCPEYXgddCibvyiOuF6bh=XBRfEO_iBvfAgukqztvtYWQ () mail ! gmail ! com
[Download RAW message or body]

As an end goal, great!
As a development strategy, not so much

If you try and redesign every KCM in one go, you'll get burned out and not
finish. There's literally 95 of the damn things (including kinfocenter) and
growing.
It will be too much of a daunting task to discuss let alone implement in
one go and it will end up with absolutely nothing happening.

Having a generic template/rules and vision for all KCMs makes sense - but
then the task needs to be split up into managable incremental changes for
the sanity of both parties.

David

[Attachment #3 (text/html)]

<div dir="ltr"><div><div><div><div>As an end goal, great!<br></div>As a development \
strategy, not so much<br></div><div><br>If you try and redesign every KCM in one go, \
you&#39;ll get burned out and not finish. There&#39;s literally 95 of the damn things \
(including kinfocenter) and growing. <br>It will be too much of a daunting task to \
discuss let alone implement in one go and it will end up with absolutely nothing \
happening.<br></div></div><br></div><div>Having a generic template/rules and vision \
for all KCMs makes sense - but then the task needs to be split up into managable \
incremental changes for the sanity of both \
parties.<br></div><div></div><div></div><div></div><div><br>David<br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]