[Sugar-devel] [PATCH sugar 0/7] Remove last hippo occurrences from the shell

[Simon Schampijer]

On 08/06/2012 02:18 PM, Sascha Silbe wrote:
> Simon Schampijer <simon at schampijer.de> writes:
>
>> This is a patch series to make the Sugar shell hippo free. Based on the
>> work that has been done in [1] and [2]. It incorporates the patch from
>> Sascha to move the EventIcon into the shell temporary.
> [...]
>
> Thanks for the patch series and especially for the detailed
> descriptions, they are rather helpful!
>
> One thing I noticed while working on the UI tests (or rather the
> prerequisite, making Sugar "accessible"): The Owner Icon is the _last_
> entry in the list, at least for the Home View. Can we make it the first
> one instead (without going to great lengths)?
>
> With the version I tested, there was also some issue with positioning;
> IIRC the Owner Icon was off-center. Has this been fixed? Are there any
> (other) known bugs?
>
> I've discussed the approach for both the hippo removal series and the
> GTK3 port with a couple of community members over the past few weeks and
> we agreed that we should focus on the architecture (i.e. external API,
> internal API, interactions with other components / APIs) and work
> towards merging the patches sooner rather than later. We fully expect
> there to be major bugs, but by merging early we enable a) widespread
> manual testing and b) development of automated UI tests that can verify
> the GTK3 port against the current behaviour of the GTK2 version. Unless
> we can't solve a number of technical issues [1] with accessibility
> support, my plan would be to do things in this order:
>
> 1. Merge hippo removal patch series.
> 2. Finish and merge accessibility patch series. It should be complete
>     enough to test all major parts of the UI. Accessibility support for
>     humans (e.g. using screen readers) is only a side effect at this
>     stage, not a goal. Help with this effort (especially fixing the
>     current blockers [1]) would be quite appreciated.

Is there a branch to look at the scope of this work? What is the 
timeframe for this? Do you have some more background info on the 
subject, e.g. a Feature page.

Simon