I Remember those days... You, Will Pearson and the other guys defining the project, coding and implementing the scripts for the JAWS interface. That was quite a team! Your scripts have served many Visual Studio and Express users for several years and are the backbone of accessibility for those applications. I use WindowEyes, still waiting for the new version to see how it handles all that, so have not used the scripts. That said, almost everyone else who works in any of the Visual Studio or Express modules use your scripts. You guys did a really nice job and I hope that others will do as well going forward so we can have blind folks using Visual Studio and, or, the Express modules for years to come.
go get them and Good luck JAWS guys... Rick USA----- Original Message ----- From: "Ken Perry" <whistler@xxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Thursday, October 28, 2010 9:29 AM Subject: RE: vs 2010 jaws project
Well I want to point out it was us on this list that made those current scripts. All you have to do is fix them. Unfortunately like some of the other original script makers I just don't have the time to do it right now it's time for others who need it to step up. Here is some hints. First learn to use the home row now known as the script utility. The new key press for this is Microsoft-insert-key pad minus, If you haven't used it you need to learn it if you're going to play with the scripts.Second while I didn't use it some of the script writers find windig by Jamala very good program to find out what is on the screen., I know it's on Jamal's site I just don't know the address so maybe he will post it. Back up you current scripts or just keep an install of the current 2005 scripts. That way when you screw them up so bad you can just reinstall.The big thing is though just dive in. Get the 2005 scripts compile them and make sure they are loading by doing insert q in visual studio 2010. If theyare loading then do insert - f2 and bring up the script editor and readthrough the current scripts. After that you should have an idea of what tochange to make the current one work.I would bet the intelesense code is what is causing the problem in the codeeditor in 2005 I had to do a lot of strange window crap to make it work.Then I think Jamal did some changes to it to. I am betting some of the new intelesense stuff is much easier to script for but the old code is probablymaking a mess out of it. So anyway I guess what I am saying is the only way these scripts are going to get modified if someone here has the time to do it. I have 2010installed but I am working on a project outside of VS right now and I can't promise I will be back into it till after next summer and who the heck knowswhat Microsoft will do between now and then. Ken -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Rick Watson Sent: Thursday, October 28, 2010 8:54 AM To: programmingblind@xxxxxxxxxxxxx Subject: RE: vs 2010 jaws project Good morning listers, Just to add to this discussion, I have been trying to get this to work and we will also need to focus on menus as well as designers. Not just the code editor. Rick -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui Sent: Thursday, October 28, 2010 8:46 AM To: Justin Daubenmire; programmingblind; Program-l Subject: Re: vs 2010 jaws project Hi Justin, I am hereby copying the ProgrammingBlind and Program-L lists in the hope that others interested in the project will get in touch with you. Jamal -- Original Message -- > Hi Jamal, > > For jaws to work with visual studio 2010 an add-in is going to need to be programmed by the community. > > I would be willing to manage this project if we have enough people wanting to help. > > We would need to setup a project on www.codeplex.com and I could do that for us. > > Then participants would need to install TortoiseSVN to perform commits to the repository. > > The plug-in would be an open source effort and I'd prefer to program it in c#.net which is just personal preference though. > > Here are a few links to information that could get us all started. > > Visual Studio 2010 Editor Samples > Several samples showing how to extend the new WPF-based editor in Visual Studio 2010. > http://editorsamples.codeplex.com/ > > How to: Control the Code Editor (Visual C#) > http://msdn.microsoft.com/en-us/library/ms228776.aspx > > If anyone is interested please have them contact me directly at jdaubenm@xxxxxxxxxx > > Thanks! > > > Regards, > Justin > > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind ECKE RANCH Providing Integrity, Innovation, & Grower Solutions for 3 Generations! This communication (including any attachments) may contain privileged or confidential information of Paul Ecke Ranch and is intended for a specific individual. If you are not the intended recipient, you should delete this communication, including any attachments without reading or saving them in any manner, and you are hereby notified that any disclosure, copying, ordistribution of this communication, or the taking of any action based on it,is strictly prohibited. __________ 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