[Sugar-devel] [DESIGN] New share button style

[Gary Martin]

On 17 Jun 2010, at 06:56, Aleksey Lim <alsroot at member.fsf.org> wrote:

> On Thu, Jun 17, 2010 at 01:42:58AM -0400, Frederick Grose wrote:
>> On Thu, Jun 17, 2010 at 1:07 AM, Aleksey Lim <alsroot at member.fsf.org> wrote:
>> 
>>> On Thu, Jun 17, 2010 at 04:47:30AM +0000, Aleksey Lim wrote:
>>>> On Thu, Jun 17, 2010 at 12:09:24AM -0400, Frederick Grose wrote:
>>>>> On Wed, Jun 16, 2010 at 11:41 PM, Aleksey Lim <alsroot at member.fsf.org
>>>> wrote:
>>> 
>> 
>> 
>> ...
>>> 
>> 
>> 
>>>> This enlivens the interface, and should only be a compliment to the more
>>>>> standard 'busy' cursor because the gray-scale tone changes of the
>>> pulsing
>>>>> can be missed in suboptimal viewing conditions.
>>>>> 
>>>>> There are several situations where a busy cursor is needed. Among them
>>> are
>>>>> these:
>>>>> 
>>>>> http://bugs.sugarlabs.org/ticket/405
>>>>> http://bugs.sugarlabs.org/ticket/851 or
>>> http://dev.laptop.org/ticket/3617
>>>> 
>>>> Not trying to argue but for me busy cursor means that the whole
>>> application
>>>> is in suspended (more or less) state, but in case of share button,
>>>> activity could be used as usual.
>>>> 
>>>> There is also another reason against setting cursor. ShareButton is only
>>> low
>>>> level widget which is not aware of high level use cases where global
>>> setting
>>>> like changing cursor is unaccessible (or sounds overkill).

+1, and also in a touch based UI there is no cursor ;)

>>> 
>> 
>> Yes, those are good reasons not to modify the cursor in the Activity sharing
>> case.
>> 
>> For the general case that you suggested, the throbbing icon is a nice
>> feature, but to serve those with low vision or in a difficult viewing
>> environment, a small, high-contrast element or badge (perhaps a small stop
>> sign, or just a small x as a badge on the icon)  should be added.

Hmmm. A stop sign or small x icon badge icon would be confusing I think, as you can currently neither stop or cancel via the toolbar button. The pulsing provides vastly more status information from where we are right now, which is zero feedback. Adjusting the pulse frequency and pulse contrast range could give some scope for improvement.    

If we need additional new high-contrast elements for the visually impaired, we should tackle that as a separate design task so as not to block on current progress. I'm sure there are more pressing features we need for that group (global font size controls, screen zoom shortcuts, screen colour reverse, audio feedback, global text to speech, etc).

>> 
>>>> 
>>>> What about just making ShareButton inactive while changing status?
>>> 
>>> http://people.sugarlabs.org/~alsroot/tmp/share-meornu-sensitive.ogv<http://people.sugarlabs.org/~alsroot/tmp/share-menu-sensitive.ogv>
>> 
>> 
>> That would work in the successful or quick failure cases, but if there was a
>> failure, and the process was stuck retrying, the static signal would not
>> provide the information about process state.
>> 
>> See
>> http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Sugar_Interface/Controls/Indicators
>> for
>> some other ideas on how to badge the icon with process state information.
> 
> To be honest I was planing to use alerts to notify about sharing errors
> with message like "Cannot make it Public, fallback to Offline", imho
> this kind of fails is critical enough to use alserts.

+1

Regards,
--Gary

> 
>> 
>> Thanks again!        --Fred
> 
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> 
> -- 
> Aleksey
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel