Relevant bug report to the discussion:
https://bugs.kde.org/show_bug.cgi?id=302067
I am in favour of any of the proposed solutions.
I think even if we went for option 2, it still makes a lot of sense to
change the existing code for desktop components, just so it's easier
to read. This also allows
On Thursday 13 December 2012 16:41:58 Aaron J. Seigo wrote:
> I currently favour the second solution (making Switch a Checkbox on
> desktop),
+1
Cheers
Martin
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasm
A Quinta, 13 de Dezembro de 2012 15:17:42 Daniel Nicoletti escreveu:
2012/12/13 Nuno Pinheiro
>>you guys know the mains reason for radio butons and check boxes beeing
>>kiiled
>>on the touch world dont you?
>My Android 4 phone has tons of checkboxes...
and you say that as if it was a good thi
2012/12/13 Nuno Pinheiro
> you guys know the mains reason for radio butons and check boxes beeing
> kiiled
> on the touch world dont you?
>
My Android 4 phone has tons of checkboxes...
They are shrodingers cats, wile you pressthem they are at the same time
> bowth
> pressed and unpresssed since
2012/12/13 Aaron J. Seigo
> On Thursday, December 13, 2012 14:00:51 Daniel Nicoletti wrote:
> > I really don't think one replaces the other. I have switches and
> checkboxes,
> > on my Android phone and I clearly sees that depending on the context it
> > fits better.
>
> yes, on touch (such as An
A Quinta, 13 de Dezembro de 2012 17:16:32 Aaron J. Seigo escreveu:
> On Thursday, December 13, 2012 14:00:51 Daniel Nicoletti wrote:
> > I really don't think one replaces the other. I have switches and
> > checkboxes, on my Android phone and I clearly sees that depending on the
> > context it fits
On Thursday, December 13, 2012 14:00:51 Daniel Nicoletti wrote:
> I really don't think one replaces the other. I have switches and checkboxes,
> on my Android phone and I clearly sees that depending on the context it
> fits better.
yes, on touch (such as Android type use cases) we'll be keeping bo
I really don't think one replaces the other. I have switches and checkboxes,
on my Android phone and I clearly sees that depending on the context it
fits better.
I think what's missing is a switch widget on the desktop and guidelines when
to use either of them.
For example, in print manager I used
On Thursday 13 December 2012, Aaron J. Seigo wrote:
> * implement Switch in the desktop components as a checkbox.
>
> Pros: this is very easy to do (API compatible; just need to move Switch.qml
> to touch components and make a new Switch.qml in the default desktop
> components that simply creates
On Thu, Dec 13, 2012 at 9:11 PM, Aaron J. Seigo wrote:
> hi ...
>
> so we have both Switch and Checkbox items in the QML. we have discussed
> previously and decided to keep using Checkbox on desktop (for consistency
> with
> the rest of the desktop UI if nothing else), though w
hi ...
so we have both Switch and Checkbox items in the QML. we have discussed
previously and decided to keep using Checkbox on desktop (for consistency with
the rest of the desktop UI if nothing else), though we favour Switch on touch.
i'm already noticing incosistencies creeping in, ho
11 matches
Mail list logo
