[nvda] A suggestion for Josh

Josh, someone as enthusiastic as you should really study to become a programmer 
for NVDA.  I think that if you spent some time reading the Python programming 
manuals that you could in time get all of the features in NVDA that you are 
looking for.  Each of these programmers have done just that.  They see a 
feature that they wish to have included into NVDA and start to program it.  I 
will point you to some websites that can get you started.
1.  www.python.org
2. http://msdn2.microsoft.com/en-us/library/aa286482.aspx
On the MSDN website you will be able to find all kinds of info on MSAA, what is 
possible and what is not.  If you are interested, I am also working on my own 
personal project in Visual Basic 6.  What it is is my own screen reader totally 
aside from NVDA.  Four years ago, I did not even know what MSAA was, much less 
how to program for it.  But through studying things for myself and a bit of 
trial and error, I now have the working source code to show for it.  Keep in 
mind, that it is ok to pass along a suggestion about an open source project but 
it can only happen if the programmer's are able or have the time to do such 
things.  The nature of open source software is that the people that work on 
open source software are usually doing it in their spare time or because they 
want to.  Open source software on the other hand does not mean that the results 
will happen in a day or will even happen at all.  In most cases though, the 
reason it does not happen is because the group of programmers that are working 
on it just do not have the knowledge needed to do the work at the time.  But, 
mostly it is because they don't have the time themselves to do it.  I hope you 
understand that you too could contribute to the development of NVDA but with it 
being an open source project you can't expect it to happen instantly.  Your 
pocket NVDA is a very good idea, and possibly when the main source of NVDA is 
developed a bit further it may also happen.  But please understand that the 
project is what it is right now and it is always changing.  One person's 
suggestion may be duely noted but you can't expect it to be done if you are not 
the one willing to program it.  It is fine to post a suggestion but to press 
and press it will only make it take that much longer for it to get done.  I am 
of the feeling that nothing is impossible when it comes to software but it 
takes time and may not happen tomorrow.  I am also of the mind that if it is 
not getting done the way I need it done I will investigate it myself and 
program it myself.  But just like posting my suggestion and hoping that someone 
feels the same it does not happen overnight.  So, I hope that you will take my 
own personal suggestion and learn the Python language and make that video 
intercept driver, Pocket NVDA, ESpeak inflection etc. happen.  I am more than 
sure that if you begin to program it and run against something you need help 
with there will be someone out there that will be more than willing to give you 
a pointer or two.  Hope this suggestion helps.

Other related posts: