[Sugar-devel] [DESIGN] Record UI
gonzalo at laptop.org
Thu Mar 31 09:29:20 EDT 2011
Thanks Gary and all the team.
On Thu, Mar 31, 2011 at 9:56 AM, Gary Martin <garycmartin at googlemail.com>wrote:
> Hi Gonzalo,
> On 18 Mar 2011, at 15:15, Gonzalo Odiard wrote:
> > I have prepared mockups about the changes I want to do in the Record UI.
> > The changes were discussed with Simon Schampijer and we take ideas from
> > Tom Staubitz.
> Just following up from Sunday's design meeting:
> See the above log for details, but here's a quick summary:
> - place the chronometer combo in the secondary toolbars, as opposed to the
> main toolbar
> - write each object to Journal upon its creation rather than trying to
> write all of them at once on an Activity switch or Stop (which can feel like
> a crash/hang if you have recorded more than a few new objects)
> - remove the (i) info icon from the toolbar and instead badge each media
> thumbnail on the bottom right corner with an info widget (icon still to be
The idea with the (i) button in the main toolbar was make a explicit
difference in the UI between the play/reproduce use and the recording use.
The icon is not good (was a temporary icon only)
> - use the Journal detail view API explicitly for editing individual object
> metadata information, rather than the custom info/take notes side bar, see
> Browse and its download complete alert for example code. We standardise on
> an edit details UI for all Activities that want to edit their metadata at
> any time, an existing proposal already being worked on .
Are you talking about the "Show in Journal" button? I think is not a good
idea for the workflow, but can be a fist step, until we have the detail view
- camera icon should be the one as seen in sugar-artwork for
> camera-external, need a similar styled icon for video (Walter has also
> recently started using camera-external in Turtle Art/Blocks)
- I suggested the sugar-artwork microphone icon (lips) would be good for the
> audio recording icon (I believe it was originally designed for use as the
> device icon for a proposed microphone input gain control palette). We didn't
> formally +1 in the meeting, but worth considering if you don't find it
I think the lips icons is better to text to speech (I am using it in Read
We need a coherent set of metaphor here.
What will be represent the icon? The action done by computer or the action
done by the child?
Also, we can record music too, no only talking.
> There is still some concern over the user interaction for a primary tool,
> with sub-toolbar, triggering a full screen canvas change (e.g. as mocked up
> in your Record camera vs video vs audio, and my Memorize play vs create UI
> modes), as it might be confusing to get back out of a mode (especially when
> triggered unexpectedly by hover delay). I'll make a test activity with this
> interaction for next Sunday's design meeting and see how it feels.
Yes. Can we disable the hover delay triggered change? May be we can use a
RadioToolButton and display the sub-toolbars when the button is toggled?
 Option 1. from Christian's 'detail view anywhere' mockups
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel