Hi Will I pull from git and will gladly help test. Aside from using Orca normally and reporting anything out of the ordinary, are there any special conditions to keep an eye out for and test? From what you're saying it doesn't sound like it, but it never hurts to ask. I'll not be able to test the braille parts as I don't use them, but I'll be sure to keep an eye on anything out of the ordinary with speech or presentation. I think this is a great idea, and I definitely like the sound of improving Orca's performance :). On Fri, 2009-05-29 at 13:49 -0400, Willie Walker wrote: > Hi All: > > We're making some needed structural changes to the Orca code base that > will have an impact on the speech generators, the braille generators, > and the where am I code. > > Ideally, this will not have an immediate impact on you as a user. That > is, Orca should continue to provide you with the same presentation of > information that you were getting before these changes. These changes, > however, enable users to change the contents and ordering of what Orca > presents, and also allows users to specify different voices to be used > for different content with very fine granularity. This also opens the > door for adding audio cues down the road. We plan on using this to > improve the performance of Orca as well. > > So...what does this mean to you? > > 1) These changes are for the current development release. They will not > be backported to any stable releases. So, that means you will only see > them on the master branch and they will only go into GNOME 2.27.x > releases and beyond. They will not be put into GNOME 2.26.x releases or > earlier. > > 2) We're still very early in the GNOME 2.27/2.28 release cycle, so this > is the appropriate time for us to make these kinds of changes. As we > make these changes, we do lots of testing. These are substantial > changes, however, so breakages may have accidentally snuck in. My > apologies in advance for those issues. With your patient testing and > constructive feedback, we will identify and fix the problems before the > GNOME 2.28 release this fall. > > 3) The first phase (the speech generator refactor) was checked in to the > master branch less than an hour ago. This means that those of you > pulling from git will see the changes the next time you pull. If you > are someone who pulls from git and uses the master branch, please help > us by testing with the latest code and providing your constructive > feedback. Ideally, you should notice NO DIFFERENCES. > > 4) We're not ready to write docs or teach you how to modify the > formatting yet. When we're done with all the phases, we hope to write > something up for you to use. Please don't ask us how to customize your > environment until we are done with all the phases. > > For the Orca team, > > Will > _______________________________________________ > Orca-list mailing list > Orca-list gnome org > http://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 > Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
Attachment:
signature.asc
Description: This is a digitally signed message part