I did neglect to publicly state that I will be putting in considerable effort this coming week into getting the VS2010 scripts back up to par. We'll see how far I get. -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Rodney Haynie Sent: Wednesday, November 17, 2010 8:39 AM To: programmingblind@xxxxxxxxxxxxx Subject: RE: the plug-in I currently have an FS Case # for JAWS 12 for why the menu bar becomes unreadable in a simple progression The menu bar will drop, and you can arrow up and down and across, but the menu items are not read. . And in that progression , the JAWS cursor was reading information from my desktop even though it was not visible on the maximized VS2010 screen. As we already mentioned a couple times before JAWS 11 does not show this bug. I think it is pretty clear that two solutions would be great at this point. One is to get VS2010 scripted with JAWS to the same level the current VS2005/2008 scripts work for those releases. Second is the plug-in effort. -Rodney -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Wednesday, November 17, 2010 7:15 AM To: programmingblind@xxxxxxxxxxxxx Subject: RE: the plug-in The reason they only have basic support is the same reason it has never really worked well. If you call FS they don't support it at all. We are the ones that wrote the scripts those of us on this list. The Jaws scripts can easily fix the text editor if you have time to do it. Ken -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Justin Daubenmire Sent: Wednesday, November 17, 2010 1:50 AM To: programmingblind@xxxxxxxxxxxxx Cc: program-l@xxxxxxxxxxxxx Subject: Re: the plug-in Hi all, The reason I opted to go the plug-in/Addin route was because jaws version 12 support of WPF and UI Automation is in the early trial/error phases. This potentially means that scripting jaws may not be the quickest route to getting reliable support into vs 2010 for people who need it fast for work or college. More than likely this is why fs only has basic support for the code editor currently in vs 2010. The addin would bring reliable speech to jaws and perhaps other screen readers if others would want to join the project and program the support into the addin project. That would be awesome! The addin does not have to be just for jaws, it could be for any screen reader if enough volunteers contribute. /Justin On 11/16/10, The Elf <inthaneelf@xxxxxxxxxxxxxx> wrote: > its been discussed but I don't think it's gotten very far. > > I think ken Perry poked into it some and decided that the 2008 ones could be > reconfigured easy enough but that was the last I herd of it. > > inthane > Moderator, Blind Access Help > Owner: Alacorn Computer Enterprises > Specialists in customized computers and peripherals > - own the might and majesty of a Alacorn! > www.alacorncomputer.com > proprietor, The Grab Bag, > for blind computer users and programmers > http://grabbag.alacorncomputer.com > > ----- Original Message ----- > From: "Justin Daubenmire" <jdaubenmire@xxxxxxxxx> > To: <programmingblind@xxxxxxxxxxxxx> > Sent: Tuesday, November 16, 2010 9:10 AM > Subject: Re: Qiestopm Re: the plug-in > > >> Hi guys, >> >> Is there already a vs 2010 plug-in being developed? If yes, I was >> unaware of it and perhaps we can join our efforts. >> >> Please let me know. >> >> Thanks! >> >> /Justin >> >> On 11/16/10, Alex Coleman <AlexC@xxxxxxxxxxxxxxxxx> wrote: >>> Likewise. >>> >>> I am interested in accessibility of VS 2010 Professional, as that is >>> what we have adopted here. >>> >>> >>> >>> >>> >>> From: Mark Matthews [mailto:mark.matthews53@xxxxxxxxxxxx] >>> Sent: Tuesday, November 16, 2010 11:17 AM >>> To: programmingblind@xxxxxxxxxxxxx >>> Subject: Qiestopm Re: the plug-in >>> >>> >>> >>> I'd thought I'd start a new thread as this is to do with the plug-in, >>> but not related to Justin's project. >>> >>> >>> >>> Apologies if this is rather elementary, but could someone explain, or >>> point me to information about how the plug-in actually works, and I'm >>> also curious as to why it only works with the Professional version - >>> would I be on the right lines by assuming the utility uses components >>> which aren't present in the Express? >>> >>> >>> >>> Also, I'd like to take the opportunity to thank the team for there >>> excellent work on the 2005/2008 scripts. After much fiddling round, I >>> got VS2008 express functioning fully from the ISO installation. I doubt >>> very much if I'll ever reach even half the standard of Programmer as >>> some of the list members, never the less its always been a subject that >>> I've been interested in, and I'm thinking no knowledge is wasted >>> knowledge. >>> >>> >>> >>> Mark >>> >>> >> __________ >> View the list's information and change your settings at >> //www.freelists.org/list/programmingblind >> > > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind