Hi Brandon,
Eventually, I'll probably create a screen reader module for the engine given the fact that is something many game developers and gamers want to have. It shouldn't be too difficult to create as most screen readers expose their APIs via a COM interface. However, its probably not something I will use myself for the simple fact one of the purposes I'm developing this engine is to help promote game development for Mac OS and Linux as well as Windows. If I tie my games to a platform specific screen reader like Jaws, Window-Eyes, etc I've just defeated one of the primary features of writing this engine in the first place.
So in answer to your question no I won't be adding direct screen reader support to Final Conflict. At least not initially. I'm rewriting the game in Python primarily so I can play it on my computers which all run Linux as the primary OS, and I wouldn't want to have a bunch of Windows dependencies I'd have to remove just to compile a cross-platform version for Mac and Linux users. So as far as speech output goes I'll probably end up using something like pyttsx which uses Sapi on Windows, Espeak on Linux, and something else on Mac.
Cheers! On 3/30/2012 5:03 PM, Brandon Misch wrote:
will the engine have screen reader api support and if not will fc2.0 have it for people who just want to use there readers and not sapi or recorded speech?
--- Gamers mailing list __ [email protected] If you want to leave the list, send E-mail to [email protected]. 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://www.mail-archive.com/[email protected]. If you have any questions or concerns regarding the management of the list, please send E-mail to [email protected].
