Hi Quentin, Thanks. I'll take a look at your API, and let you know what I think.
As far as an open source project I think that would be a good idea, but I see one potential problem with that and it deals with proprietary licenses. For instance, I am currently in communication with Dolphin--the makers of SuperNova---and they seem to be overly protective of their screen reader API and documentation. The first thing they said when I asked about it is that I'd have to sign a non-disclosure agreement and fill out some legal forms before they would even discuss it with me. That kind of proprietary and secretive license, prevents anyone of adding support for SuperNova in any kind of open source project. As for Window-Eyes I just got the developer information today and it looks fairly straight forward. Beginning with Window-Eyes 7 GW Micro has deprecated the GWSpeak.dll API in favor of connecting with Window-Eyes through its script interface. It doesn't seem all that complicated, but it does feel like an odd way to send messages to and from a screen reader. In any case I'm sure I can help you with Window-Eyes. I've used Window-Eyes for at least twelve years---ever since Window-Eyes 3.1 came out--so I have the experience to help with it. The last version I got before switching to NVDA was 7.5, and therefore have a fairly current release to do testing with. I hope to have Window-Eyes support added to my engine sometime before the week is out now that I have the end user documentation and Window-Eyes SDK in hand. Cheers! On 11/1/11, QuentinC <quent...@cfardel.net> wrote: > Hello, > > I don't know much about licensing issues and I'm not sure of what to do > in that area. I also dont' really know what to do about giving an access > to the source code or not. One thing is sure, the project is very young, > nothing for future is really decided, and the source code isn't made to > facilitate reading (I don't want to waste time for that). > > A binary only version is online here: > http://vrac.quentinc.net/ScreenReaderAPI.zip if you wish to take a look > > > Since gatehering information about screen readers API is quite hard, it > might be nice to be able to collect all we know at the same central > point and to start an open source project. I don't know. Maybe we could > talk in private to discuss what would the best thing to do. > The benefit of associating could be good: for example you are a > specialist of window eye, and myself I don't know that scrren reader at > all (I was even unable to install a demo version on a XP VM), so you > could probably improve the code concerning window eye. > > > --- > Gamers mailing list __ Gamers@audyssey.org > If you want to leave the list, send E-mail to > gamers-unsubscr...@audyssey.org. > You can make changes or update your subscription via the web, at > http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. > All messages are archived and can be searched and read at > http://firstname.lastname@example.org. > If you have any questions or concerns regarding the management of the list, > please send E-mail to gamers-ow...@audyssey.org. > --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://email@example.com. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.