Re: [orca-list] Tackling 3.2 isms through tutorials?

[Jude DaShiell <jdashiel shellworld net>]

Please put tutorials for gnome 2.x and earlier in their own section of 
the website or tag those tutorials as specifically applying to gnome 2.x 
and likewise tag the new tutorials for gnome 3.0 and gnome 3.2 and write 
up the expected versions of gnome and expected versions of orca in those 
tutorials.  That way at least new users will either find material that's 
appropriate to what it is they're running or can ask where it is to be 
found.
If the day comes when xfce is supported by orca such extra documentation 
work will be invaluable.

On Thu, 13 Oct 2011, Thomas Ward wrote:

> Hi joanie,
>
> I think that is an excellent idea. Many of us, such as myself, don't
> have 3.2 packages available so are in the sucky position of compiling
> Gnome 3.2 and Orca from scratch using build scripts etc. It would be
> especially helpful if we have some kind of baseline to compare our
> output to when testing the latest Gnome apps, libraries, etc. If
> something shows up on my PC or distribution I can at least look at the
> docs and see if this bug has been reported, if it is same/different
> from the expected output, and then determine if it is something I did
> or the developers did to cause the problem. A tutorial such as you
> suggest would be invaluable for testers. I myself have just acquired a
> new PC, and I plan to use my old one for KDE and Gnome unstable
> testing so I personally would find tutorials such as this a great
> resource.
>
> On 10/13/11, Joanmarie Diggs <joanied gnome org> wrote:
> > Hey guys.
> >
> > As you all surely know by now a *bunch* of changes in a *bunch* of
> > different places within GNOME occurred: Initially in 3.0, and then again
> > in 3.2. Thus for any given issue you are experiencing:
> >
> > * It might be an Orca bug.
> > * It might be a toolkit bug (Gtk+ 3, Clutter, etc.).
> > * It might be an application bug.
> > * You (or your distro) might have borked things in the transition.
> > * What you think is on the screen and what's actually there might be
> >   different. Keep in mind, GNOME 3.x changed quite a bit design-wize.
> >
> > I think we can start addressing many of these problems through the
> > process of creating tutorials. In particular, here is what I'm
> > proposing:
> >
> > 1. I start writing short tutorials on how to use Orca with <insert fancy
> >    new GNOME 3.x feature here>. I'll include keystrokes, a description
> >    of exactly what's going on on the screen, and what Orca should say as
> >    a result. This will be our baseline definition of expected behavior
> >    in GNOME 3.2.
> >
> > 2. In the process of doing item 1, I will undoubtedly find bugs. They
> >    may be known issues; then again, they may not. Either way, I'll
> >    triage, file bugs, and note these in the tutorials.
> >
> > 3. Having written a short tutorial, it will be the mission of y'all to
> >    try what I wrote and verify it. If you find something different,
> >    let's see if we can find another user with the same results. If the
> >    only users who can reproduce the problem are users of the Foo distro,
> >    then the Foo distro needs some debugging and triage. If the only user
> >    who can reproduce the problem is you, let's rule out settings and
> >    locale. And if things are still broken just for you, well, then we
> >    have to call that an anomaly and move on I'm afraid, but hopefully
> >    others will be able to assist. While all y'all are doing step 3, I'll
> >    go back to step 1 and crank out another.
> >
> > 4. Attila, if memory serves me, is Mr. Tutorial message. <smiles> So
> >    with any luck we can count on him for patches with tutorial messages
> >    which can be optionally turned on and/or invoked via whereAmI.
> >
> > 5. Once we have a handle on what the "average" Orca user is seeing and
> >    have nifty new tutorial messages in place, we update the original
> >    English short written tutorial, we add it to a to-be-created section
> >    in Orca's docs so we can get it localized by the always-awesome i18n
> >    team and shipped by the distros.
> >
> > 6. We recruit folks to do audiovisual tutorials based on the finalized
> >    written one so people can follow along and experience it before
> >    trying it.
> >
> > Thoughts?
> > --joanie
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > http://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at
> > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Netiquette Guidelines are at
> > http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp

Jude <jdashiel shellworld net>
If I got a nickel for every message I've already sent supporting Microsoft
Windows and its applications I'd have enough to retire on comfortably no
matter what the stock market did.