Re: [orca-list] Is any Technical documentation or technical reference Document available for Orca3.X ?

[Alex Midence <alex midence gmail com>]

I wonder if anyone has thought to use something like Doxygen to autogenerate
some rough-hewn technical documentation which can then be embellished up to
spec as it were.  Would this even be a feasible idea?  I've seen several
inquiries throughout the last couple of years I've been on this list asking
for just exactly this sort of technical documentation.  Trouble is, it's a
tedious, thankless job to produce and keep up with.  It's literally
deserving of its own maintainer so that it stays current.  I imagine finding
someone willing to maintain the technical docs wouldn't be so hard if only
the initial writing were completed before such a person took up the
maintenance task.  I find myself wishing I could do something towards this
but I lack the necessary expertise to do a proper job of it and don't want
to make a hash of things by hamfisting it.  Any thoughts by anyone?  Is my
assessment of things even correct?

Alex M


-----Original Message-----
From: orca-list [mailto:orca-list-bounces gnome org] On Behalf Of
Krishnakant Mane
Sent: Thursday, February 27, 2014 12:52 AM
To: orca-list gnome org
Subject: Re: [orca-list] Is any Technical documentation or technical
reference Document available for Orca3.X ?

Hi daryashil,
I am also looking for the same and off late started to read the Orca source
code.
Could you please mail me off the list, I wish to know what do you do and
what made you get into Orca programming.
Happy hacking.
Krishnakant.

On 02/27/2014 05:09 AM, Jason White wrote:
> Dhairyashil Bhosale <dhairyashil bhosale584 gmail com> wrote:
> >                 Any One have Technical documentation or technical 
> > reference Document available for Orca3.X ?  If available please 
> > forward me for understanding how Orca works or what changes done in 
> > Orca 3.x for gnome 3 interface.  .  .
> The only up to date technical documentation that exists consists of 
> comments in the Orca source files. There may be a paper describing 
> Orca available on the Web, written when Orca was first created, but it 
> won't help much with the questions you're asking.
>
> To make changes to Orca, you need to know Python and be prepared to 
> read and understand the source code. It's the same with any software, 
> of course: you need to understand the language in which it's written 
> and be prepared to work with the sources.
>
> _______________________________________________
> 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