Hi Will,
Please also check the other designers, if you're not doing so already.
E.g.
the component designer etc. I suspect they may be very similar to the
forms
designers, but it's worth a look. I had assumed that all the designers
were
based on the same thing, and thus if the Windows form designer was catered
for, then the web form designer should also work. But you never know with
these things.
David Lant
I.T. Consultant
Consultancy & Development
ICT Services
Tel: (01392) 382464
Devon County Council accepts no legal responsibility for the contents of
this message. The views expressed do not reflect those of Devon County
Council.
-----Original Message-----
From: Will Pearson [mailto:will-pearson@xxxxxxxxxxxxx]
Sent: 09 September 2005 15:52
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: JAWS scripts for .NET Framework
Hi Justin,
Yes, it's something that we plan to cover. Both Travis and myself had a
look at the Web Forms designer whilst we were testing VS 2005, and it
implements MSAA. Most of the other dialogs involved with ASP .Net
development, such as the editor, solution explorer, etc. are the same as
they are for Win Forms development, and so incorperating functionality for
ASP .Net development isn't much in the way of additional overhead.
Will
----- Original Message -----
From: "Justin Daubenmire" <justind@xxxxxxxxx>
To: <program-l@xxxxxxxxxxxxx>
Sent: Friday, September 09, 2005 3:02 PM
Subject: [program-l] Re: JAWS scripts for .NET Framework
Wil,
will you also be putting in support for asp.net forms and control /
web
development? This was lacking in the fs vs 2003 scripts.
Justin
----- Original Message -----
From: "Will Pearson" <will-pearson@xxxxxxxxxxxxx>
To: <program-l@xxxxxxxxxxxxx>
Sent: Thursday, September 08, 2005 4:01 PM
Subject: [program-l] Re: JAWS scripts for .NET Framework
Hi Jamal,
Unfortunately they won't run with CLR applications. Each
application, as
is common with Windows applications, has a different name, and as usual,
the file name of the JAWS scripts have to match the application's name
in
order for JAWS to determine that the scripts should be used with that
application. However, the window classes used within Windows Forms
applications have class names that JAWS doesn't recognise. As a result
of JAWS not recognising the class names, it actually uses MSAA, which
for
the most part works great, especially as WinForms applications are
proxied by MSAA if there's an equivalent control within the collection
of
standard and common Windows controls. Apart from the WinForms controls
that don't have an equivalent amongst the standard and common Windows
controls, JAWS also uses the off screen model for edit controls, which
subjects edit controls to the usual stability of the JAWS off screen
model. If people wanted to, they could cut and copy what Travis and
myself are doing for WinForms edit controls and use it in their own
scripts.
We'll try and get something out before early November, it just
depends on
how busy we both are *smile*.
Will
----- Original Message -----
From: "Jamal Mazrui" <Jamal.Mazrui@xxxxxxx>
To: <program-l@xxxxxxxxxxxxx>
Sent: Thursday, September 08, 2005 5:48 PM
Subject: [program-l] JAWS scripts for .NET Framework
Hi Will and Travis,
Regarding the scripts you're developing, I'm curious whether they
would be only for blind programmers developing with the Visual
Studio IDE , or whether they would support blind users of .NET-based
applications as well, e.g., executables developed with the IDE that
incorporate the .NET runtime engine.
Also, do you think you can post beta scripts to try before the
VS2005 commercial release?
Regards,
Jamal
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
