[Dextrose] [PATCH] Resolution for ticket au#887.

[Frederick Grose]

On Tue, Sep 20, 2011 at 7:52 AM, Ajay Garg <ajaygargnsit at gmail.com> wrote:

> === Usability notes ===
>
> 1. Now, besides an interactive 'Software Update', a background
>   thread also checks for available activity updates. To prevent
>   possible collisions in a rare situation when the interactive
>   session and the background thread might run at the same time,
>   synchronization has been used.
>
> 2. When a user enters into 'Software Update' section-view,
>   exclusive control is gained. The exclusive control is
>   retained unless and until this section-view is exited
>   (via 'Cancel' or 'Ok' toolbar buttons).
>
>   If the background thread wishes to run, it waits,
>   while the user interacts with the section-view.
>
> 3. If the background thread is running, it has exclusive control.
>   If the user wishes to enter into an interactive session (by
>   clicking onto the 'Software Update' section-view-icon),
>   following happens :
>
>   a. The section-view shows 'Getting ready...' markup,
>      with the message 'Waiting for activity-update-
>      notifier thread to relinquish control...'
>

This message would be friendlier to Learners with more general terms, such
as, 'Waiting for the automatic update check to complete...'

     Thanks for the engineering and documentation!
     --Fred


>   b. The (interactive) thread waits, until the background
>      thread relinquishes control.
>   c. After the (exclusive) control is retained, the
>      interactive thread proceeds normally, checking
>      for updates, followed by user-wish of installing
>      updates.
> {...}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/dextrose/attachments/20110920/db8a47e2/attachment-0001.html>