On Sat, Aug 4, 2012 at 3:43 PM, Matthias Clasen
matthias.cla...@gmail.com wrote:
=== 6. OSK widget context provider (e.g. search vs open vs go...) ===
Matthias said there was a patch floating around for that. I looked in the
bugs with patches attached in bugzilla but could not find it. If
On 08/04/2012 07:41 AM, Emmanuele Bassi wrote:
and yet another case of i'm so nervous and irritated by criticism of our
design decisions that i'll resort to calling people stupid ...
design has nothing to do with it, sorry to disappoint the conspiracy
theorists.
just another case of
Hi,
I just went through a midnight read of this thread, might as well throw some
ideas relating to the several points which have (or have not) been made.
From a touchscreen perspective, you want to avoid spin buttons at large
cost if not all cost.
From my experience, in the context of a kiosk
hi;
once again, from the department of I didn't bother to ask, so I'll
make stuff up...
On 2 August 2012 13:52, Morten Welinder mort...@gnome.org wrote:
=== 4. Which GTK+ widgets break with touch ===
The SpinButton item from above is one example of those.
I really hope the solution is
hi;
and yet another case of I don't know that, so I'll make stuff up.
On 2 August 2012 14:11, Paul Davis p...@linuxaudiosystems.com wrote:
=== 3. SpinButton ===
[ ... ]
Another option is introducing a complete new widget targeted at touch
usage (similar to the one in iOS Garageband) [4]
hi;
On 4 August 2012 00:05, Michael Natterer mi...@gimp.org wrote:
On Thu, 2012-08-02 at 08:52 -0400, Morten Welinder wrote:
GtkSwitch bugs me. It really should just have been a styling of the toggle
button since it performs the same function with a different look. But no,
it is currently a
hi;
On 4 August 2012 14:14, Paul Davis p...@linuxaudiosystems.com wrote:
On Sat, Aug 4, 2012 at 3:50 AM, Emmanuele Bassi eba...@gmail.com wrote:
[ ... ]
and yet another case of i'm so nervous and irritated by criticism of our
design decisions that i'll resort to calling people stupid ...
On Sat, Aug 4, 2012 at 3:44 AM, Emmanuele Bassi eba...@gmail.com wrote:
GtkSwitch bugs me. It really should just have been a styling of the toggle
button since it performs the same function with a different look.
it does not perform the same action.
That is a baseless assertion. Of course
hi;
On 4 August 2012 15:18, Morten Welinder mort...@gnome.org wrote:
On Sat, Aug 4, 2012 at 3:44 AM, Emmanuele Bassi eba...@gmail.com wrote:
GtkSwitch bugs me. It really should just have been a styling of the toggle
button since it performs the same function with a different look.
it does
On Sat, Aug 04, 2012 at 03:39:05PM +0100, Emmanuele Bassi wrote:
one implies a soft action (GtkToggleButton), whereas the other
implies something similar of a hardware switch (GtkSwitch).
As every user knows, widgets relay wishes to magic pixies. I wonder if
that is soft or hard action, maybe
=== 6. OSK widget context provider (e.g. search vs open vs go...) ===
Matthias said there was a patch floating around for that. I looked in the
bugs with patches attached in bugzilla but could not find it. If someone
knows where it is would be great.
Toggle buttons and the switch widget both suffer usability problems for me.
The visual look of a button represents an action to be performed in my
mind, perhaps why it was referred to it as a soft-action? So when a button
is stateful it can create ambiguity depending on the text of the button.
The
On Thu, 2012-08-02 at 08:52 -0400, Morten Welinder wrote:
GtkSwitch bugs me. It really should just have been a styling of the toggle
button since it performs the same function with a different look. But no,
it is currently a totally separate widget not even derived from GtkButton.
I could
Hey :),
On jue, 2012-08-02 at 11:42 +0200, Simon Schampijer wrote:
Hi,
there have been several discussions around GTK+ touch support during
GUADEC. To get a good touch experience we talked about the following
points. I ordered them by priority that we set in Sugar development for
them.
Another option is introducing a complete new widget targeted at touch
usage (similar to the one in iOS Garageband) [4] which Carlos implemented
already [5]. The issue is here the height, which at least in a Sugar toolbar
could be not as ideal and introducing a new widget.
votes++. The spin
On 12-08-03 09:21 PM, Matthias Clasen wrote:
Another option is introducing a complete new widget targeted at touch
usage (similar to the one in iOS Garageband) [4] which Carlos implemented
already [5]. The issue is here the height, which at least in a Sugar toolbar
could be not as ideal and
Hi,
there have been several discussions around GTK+ touch support during
GUADEC. To get a good touch experience we talked about the following
points. I ordered them by priority that we set in Sugar development for
them. If you come across something that we missed, please comment.
=== 1.
=== 4. Which GTK+ widgets break with touch ===
The SpinButton item from above is one example of those.
I really hope the solution is neither remove anything that doesn't work
with touch or parallel widget hierarchy.
GtkSwitch bugs me. It really should just have been a styling of the toggle
On Thu, Aug 2, 2012 at 5:42 AM, Simon Schampijer si...@schampijer.dewrote:
=== 3. SpinButton ===
[ ... ]
Another option is introducing a complete new widget targeted at touch
usage (similar to the one in iOS Garageband) [4] which Carlos implemented
already [5]. The issue is here the
19 matches
Mail list logo
