Re: Proposed Orca Migration

[Willie Walker <William Walker Sun COM>]

Hi All:

In the spirit of keeping the Orca migration decoupled from the
accessibility properties dialog redesign, Bill Haneman has created
patches for control-center and gnome-session:

http://bugzilla.gnome.org/show_bug.cgi?id=348630 (control-center)
http://bugzilla.gnome.org/show_bug.cgi?id=348643 (gnome-session)

The first patch (control-center) gives preference to using 'orca' for
the exec_ats property if screen reading or magnification is desired, but
will fallback to 'gnopernicus' if 'orca' is not present on the machine.

The second patch (gnome-session) will fallback to 'orca' if the exec_ats
prefs has specified 'gnopernicus' but 'gnopernicus' is not present on
the machine.

These seem to address Shaun's migration concerns as well as Matthias'
FC6 concerns.

I'll be happy to work with the control-center and gnome-session
maintainers to roll these patches in for GNOME 2.16.

Comments?

Will
 
On Mon, 2006-07-24 at 23:02 -0500, Shaun McCance wrote:
> On Tue, 2006-07-25 at 14:48 +1200, Matthew Paul Thomas wrote:
> > On Jul 25, 2006, at 11:41 AM, Bill Haneman wrote:
> > > ...
> > > I seem to recall that there was a reason why we didn't use 'startup
> > > programs' before.  Can't remember what it was... but I seem to 
> > > remember looking at and rejecting that before.  Maybe because we 
> > > wanted the ATs to launch first?  Or is there a problem with the 
> > > 'startup programs' API/interface itself?
> > > ...
> > 
> > It might be that the accessibility settings window, because it is 
> > rarely used, could have at least some accessibility options (large 
> > text, spoken controls, etc) turned on all the time, to be more 
> > accessible to people who are trying to turn them on. It would be 
> > annoying if the Startup Programs window did that.
> 
> The objection I would raise is that our preferences menu
> is crowded, and dealing with startup programs involves
> going to the cryptic 'Sessions' preferences.
> 
> If one thinks in terms of tasks users want to perform,
> then I think the selection of the accessibility tools
> belongs in the accessibility tools dialog.  Why force
> the user off to another dialog with information that
> isn't relevant to what they need to do?
> 
> If we don't want to shoehorn all the ATs into three
> categories, maybe we could just have a list box with
> all the ATs in it, and users could check the ones
> they want to launch.
> 
> I don't pretend to know what the best solution here
> is.  I'm just tossing around ideas, because I want
> this to happen, and I wasn't seeing anybody else
> talking about it.
> 
> --
> Shaun
> 
> 
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list