On Monday 31 July 2017 23:28:32 kainz.a wrote:
> 3. update all KCM
> This task is HUGE we are talking about 70 (by default installed KCM's) and
> additionally some other KCM's. Update all KCM's would be a big (maybe to
> big) step. So I separte the KCM's in the 4 major sections
> - 1. Appearance
g
This topic is very old and tbh my motivation was very low to start it
again, but as the feedback from the akadamy was that the plasma team want
to start with this topic again, I'm motivated again.
There are some options how to manage this task
1. wait for kuserfeedback results to found out which k
On Mon, Jul 31, 2017 at 4:15 PM, kainz.a wrote:
> Hi,
>
> should we start a redesign of ALL KCMs. Is someone interested in participate
> the mockup discussion and afterwards the code work.
>
> The idea is to redesign ALL kcms and not some specific ones so in the end
> the design language should be
Am 2017-07-31 16:15, schrieb kainz.a:
Hi,
should we start a redesign of ALL KCMs. Is someone interested in
participate the mockup discussion and afterwards the code work.
The idea is to redesign ALL kcms and not some specific ones so in the
end the design language should be for all the same, bu
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
Hi,
should we start a redesign of ALL KCMs. Is someone interested in
participate the mockup discussion and afterwards the code work.
The idea is to redesign ALL kcms and not some specific ones so in the end
the design language should be for all the same, but the layout could be
different.
Cheers
