[Sugar-devel] [DESIGN] Frame Device icon Volumes

Gonzalo Odiard gonzalo at laptop.org
Sun Aug 19 19:47:20 EDT 2012


On Sun, Aug 19, 2012 at 3:04 PM, Gary Martin <garycmartin at googlemail.com>wrote:

> On 19 Aug 2012, at 15:54, Simon Schampijer <simon at schampijer.de> wrote:
>
> > On 08/19/2012 03:45 PM, Gonzalo Odiard wrote:
> >> There are a convention about the position of the primary action?
> >> Should be the closest to the button or the first at top of the palette?
>
> The palettes reflow based on how close to a screen edge it is, so in some
> cases it might not be easily to know which end of the palette is closest to
> the button. I'd also call out that reordering a palettes content is a worse
> UI crime for consistency. At Sugar Camp Paris 2, Simon and I did mock-up a
> range of 'put the primary action by the button' type designs, until we
> realised the issues with reflow when near screen edges.
>
> So that's a +1 for top of the palette. I've always assumed this was the
> convention and implicit in the current implementation, but perhaps it's not
> explicitly documented (seemingly like so many other items).
>
>
+1 to top of palette.



> >> I think is important have this defined, and may be show it in a special
> way.
> >> In this particular case, the option is between the label, another
> action and
> >> the widget showing the size, and is not obvious.
> >>
> >> Gonzalo
> >
> > So, in this particular case, there is no primary action anymore. Left
> click will always bring up the Palette, then it is up to the user to decide.
>
> +1
>

May be is not primary in the sense that is the action executed
when the user press the left button over the icon,
but always will be a more important action.
I am thinking in doing easier to found this option.
Also I am thinking in a future where we can do Sugar more accessible,
these palettes should be keyboard navigable, and the main option
should be focused.


>
> > Let's look at another case: the Activity Palettes in the Frame (see
> activity_palette_1.png). The primary action there is to resume the
> Activity. When you click on the button that activity is resumed. The action
> is drawn right below the label. That is where I would put it as well. But
> in this case, I think the separator should then be drawn below the primary
> option (see activity_palette_2.png).
>
> Yes, for this case I think that's a reasonable amendment. The only other
> variation for this that came to mind would be to make the primary action
> text bold (as adding/moving separators might not always be the right
> treatment).
>
>
Bold could be a good option.
Should be good have a api in the palette to be able to set the main action,
and not need to add code every time, to set bold or put the separator, and
so.

(In other news:I don't lose the hope, to have a palette where we can set a
widget
instead of a text in the main area,
to be able to implement this: http://wiki.laptop.org/go/File:Frame-05.jpeg )

Gonzalo



> > Doing the same for the Volume Palette will look odd
> (volume_palette_2.png) as we have also a separator below the 'Remove'
> option as this is the Palette content (the progress bar showing how much
> space is left). Three horizontal lines in one Palette is just too much.
>
> Agreed, separators allow grouping/structure, putting separators between
> every item does not help, and is not a visual improvment.
>
> > On a related note: actually we should show the 'Show content' option in
> the Volume Palette in the Journal as well. I think it is right to leave the
> primary action there, clicking on the icon it is to switch views. But the
> primary action should be present in the Palette as well, same as we do in
> the Activity Palettes in the Frame where the primary action is 'Resume' and
> it is shown as well in the Palette.
>
> +1
>
> Regards,
> --Gary
>
> > Regards,
> >  Simon
> > <activity_palette_1.png>
> > <activity_palette_2.png>
> > <volume_palette_2.png>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20120819/8b3bfe7c/attachment.html>


More information about the Sugar-devel mailing list