Thanks Shaun!
Just to confirm: you are on board with the proposed solution for GNOME
2.16 as outlined in the discussion and implemented by the patches for
bug 348630 and bug 348643?
For GNOME 2.18, a task will be to to a better job on setting
accessibility preferences. The Ubuntu folks have do
On Wed, 2006-07-26 at 16:34 +0100, Bill Haneman wrote:
> On Wed, 2006-07-26 at 16:14, Shaun McCance wrote:
> > On Wed, 2006-07-26 at 05:26 -0400, Willie Walker wrote:
> > > Hi All:
> > >
> > > In the spirit of keeping the Orca migration decoupled from the
> > > accessibility properties dialog rede
On Wed, 2006-07-26 at 16:14, Shaun McCance wrote:
> On Wed, 2006-07-26 at 05:26 -0400, Willie Walker wrote:
> > 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 g
On Wed, 2006-07-26 at 05:26 -0400, Willie Walker wrote:
> 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=3
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=34864
BTW, I have my session set up to always launch Orca via the "Startup
Programs" GUI and it works fine. I haven't tried it with GOK or Dasher,
though.
Will
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
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
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 i
On 7/24/06, Willie Walker <[EMAIL PROTECTED]> wrote:
> Does this mean FC6 will not be GNOME 2.16?
It will be 2.16 - except for new modules which are not yet
in FC. Of course, most (all ?) of the new modules under consideration
are available in Fedora Extras anyway.
Matthias
__
Does this mean FC6 will not be GNOME 2.16?
Will
On Mon, 2006-07-24 at 19:56 -0400, Matthias Clasen wrote:
> Whatever solution you choose in the end, please make sure that
> it will continue to work with gnopernicus (it was too late for us to
> replace gnopernicus by orca for FC6)
>
> Matthias
>
Whatever solution you choose in the end, please make sure that
it will continue to work with gnopernicus (it was too late for us to
replace gnopernicus by orca for FC6)
Matthias
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail
it is more specific
> than "Re: Contents of desktop-devel-list digest..."
>
>
> Today's Topics:
>
>1. Re: Tomboy in Desktop (David Nielsen)
>2. Re: dbus building pains (Jason D. Clinton)
>3. Re: Proposed Orca Migration (Willie Walker)
>
Hi Sean, Will,
If I might chime in... I think either of Will's proposals is fine for
GNOME 2.16, with a slight preference to #2 - to move users to launching
AT at startup just like the launch other apps at startup.
Calling out "screen reader", "screen magnifier", and "on screen
keyboard" does
Hi Shaun:
I think we've all agreed that we want to replace Gnopernicus with Orca
and I think we all agree that the accessibility dialog needs work. I do
not believe the work for the two must be coupled.
If I understand your primary concern with the migration, it's that the
user who has configure
On Mon, 2006-07-24 at 19:20, Shaun McCance wrote:
> Doing Orca right in 2.16 will require some changes in core
> Gnome modules. Unfortunately, the feature and UI freeze is
> today. I'd like to outline a proposal for getting Orca in
> this release cycle.
>
> First, I don't know which module is re
Doing Orca right in 2.16 will require some changes in core
Gnome modules. Unfortunately, the feature and UI freeze is
today. I'd like to outline a proposal for getting Orca in
this release cycle.
First, I don't know which module is responsible for starting
accessibility tools on log in. Somebod
16 matches
Mail list logo
