Re: [orca-list] Programers guide for Orca development

[Mike Ray <mike raspberryvi org>]

I'll help how I can also.

Following what Krishnakant said about my last post I thought some more
about what I would like to be able to read and understand...

It reminded me of the stuff you hear from scientists who study the first
few milliseconds, or even microseconds of the life of the universe after
the big-bang.

I would like to see a timeline of what happens when a previously not
running accessible app is launched.  So, Orca is lurking and has
registered with at-spi and the user launches xyz.  What is the immediate
sequence of events?  How does Orca get to hear about xyz, pick a script
class and start responding to posted events.

I've started looking at pyatspi to see if I can contribute to this.  I
think it's as important to get a firm handle on at-spi as on Orca since
one is useless without the other.




On 02/01/2015 02:18, Alex Midence wrote:
> Wow, quite a thread.  Caused a bit of a stir.
>
> Jason:  This poster illustrates the difference between what should be
> possible and what is.  It SHOULD be possible for someone who knows
> Python to extrapolate what needs to be done via a debug file and no
> documentation.  HOwever, not everyone can and those who can say it takes
> too long.  So, dev docs are a valuable commodity if you want code
> contributions.
>
> Jose:  Thank you for being willing to step up and provide basic
> scripting guidance.  Don't worry, we  can polish what you write just
> fine.  And, if I'm ever in Brazil as I have wanted to visit for so long
> now, I'll totally get you some beer.  I learned Portuguese as a boy from
> some very good Brazilian friends from Pernambuco and others from Sao
> Paulo and Rio.  I can't write it very well but, I can speak it and read
> it just fine.  Being a native speaker of Spanish and having an aptitude
> for languages made it pretty easy to pick up. So, between your English
> and my bad Portuguese, todo vai sair bem, camara!
>
> Alex M
>
>
> On 12/29/2014 08:17 PM, kendell clark wrote:
> hi
> I'll chime in myself here. I've tried a few times to pick up orca,
> much as I tried to pick up nvda back when I used windows, and always
> eventually gave up. This isn't because of orca itself, but rather the
> layored and sometimes convoluted method of getting orca to speak
> anything. You'd think setting something as an icon and setting it's
> role would be enough, but it seems at-spi has to get exactly what it
> wants or orca has no fallback, and therefore speaks nothing. So this
> isn't orca itself, but the layor beneath it that defeated me. There is
> some sparce documentation on at-spi but it's so geeky it's way over my
> head. If I could understand at-spi I could go a long way towards
> implementing something like that nvda speaking thing I've been
> wanting. Just making orca speak text through at-spi, bypassing the
> entire dbus mess, which is yet another thing I have to try to understand
> Thanks
> Kendell clark
>
>
> B. Henry wrote:
> > > > Good points as well. Of course it's always best to get applications
> > > > to have code that complies with best accessibility practices, but
> > > > that being said not only might it sometimes be easier  to work
> > > > around issues if an app is not that well written, and I suspect
> > > > there will be times when lead devs may not be willing to accept
> > > > accessibility patches sadly, and at least for a time orca may have
> > > > to give more than it really ideally would. Also there are
> > > > relatively minor, but potentially rather helpful features that a
> > > > less than stellar coder could probably add to Orca, e.g. the
> > > > progress-bar beeps that have been discussed here a couple of times.
> > > >   I suspect there's plenty of work to go around in c++, python and
> > > > other languages...smiles
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________ orca-list mailing
> > > > list orca-list gnome org
> > > > https://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
> > > > 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
> > https://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
> > 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
> https://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
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp

-- 
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK

"The universe is full of magical things, patiently waiting for our wits
to grow sharper."
(Eden Phillpotts; from 'A Shadow Passes')

Interested in accessibility on the Raspberry Pi?
Visit: http://www.raspberryvi.org/
> From where you can join our mailing list for visually-impaired Pi hackers