RE: WPF, Win32 and Forms with UI Automation
- From: Chris Meredith <cmered@xxxxxxxxxxxxx>
- To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 18:13:27 -0800
Rick,
Any control you create on a WPF Window would be a WPF control. If you add a
Windows Form to a project, any control dropped on its design surface would be a
Windows Forms control. Win32 controls are used in unmanaged code. Of course,
we could complicate the situation further by saying that an MFC project written
in Visual C++ can also have Windows Forms controls, thus making it a "mixed
mode" project, but that gets headachy.
As far as needing Vista, that you don't need--the .NET Framework 3.0 will run
on Windows XP without a problem and gets installed when you install Visual
Studio 2008.
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Thursday, February 21, 2008 6:06 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: WPF, Win32 and Forms with UI Automation
Hi Guys:
OK, I just brought a new computer with XP Pro for my VS 2008 work, thought it
would be mor solid for awhile than Vista Business.
Now I read that there 3 classes of controls.
Win32, Forms and WPF? I think it was WPF, getting fried.
Anyway, if I write a Vb.net project and use WPF for the UI would all the
controls dropped on the WPF Design surface be considered wPF controls?
I ask because Win32 and Forms have their own Frameworks and use IAccessible or
something completely diferent than the new UI Automation interface Patterns if
I understand what I read.
I really don't want to buy Vista on top of a brand new XP Pro OS if I don't
have to but want to get started with UI Automation and the new WindowEyes
scripting to make Visual Studio and other MS Products I would like to use
really friendly.
Rick USA
----- Original Message -----
From: Chris Meredith<mailto:cmered@xxxxxxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, February 21, 2008 8:35 PM
Subject: RE: Is WPF Accessable?
As far as language preference, the whole point of the .NET Framework vis a vis
that is that it really doesn't matter what language you write in. Per my
earlier message about screen readers and C++, where C++ really comes into play
there is the fact that you can more easily call unmanaged code from managed
code, and vice versa, as I understand it.
-C-
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Thursday, February 21, 2008 5:24 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Is WPF Accessable?
Hi Sean:
I am really raw with UI Automation. I just read some about it, looked at some
code, think it was what is called client rather than provider, written in C#
and Vb.net which walked the control tree.
I am tstarting to learn to write for UI Automation and would prefer Vb.net but
could learn to work in C#.
Rick USA
----- Original Message -----
From: Sean Farrow<mailto:sean.farrow@xxxxxxxxxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, February 21, 2008 6:33 PM
Subject: RE: Is WPF Accessable?
Hi:
I am not a beta test of window-eyes, but knowing a bit about automation and
about UI automation, I woul be happy to write such a setup. I would write the
setup in a mixture of Delphi, and one of the .net languages--this could include
chrome from remobjects software.
Any volentiers and what .net language would people prefer?
Sean.
________________________________
From:
programmingblind-bounce@xxxxxxxxxxxxx<mailto:programmingblind-bounce@xxxxxxxxxxxxx>
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: 21 February 2008 23:08
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Is WPF Accessable?
Any detailed docs on the process and can it be written in Vb.net? Or, is there
something about c++ which makes it a better choice for automation coding.
WindowEyes is getting a Scripting Language using a Com Host I think they called
it and so I'm thinking of getting started messing with accessibility coding.
Perhaps automation can pick up anything the WindowEyes scripting process
misses.
Rick USA
----- Original Message -----
From: Chris Meredith<mailto:cmered@xxxxxxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, February 21, 2008 5:44 PM
Subject: RE: Is WPF Accessable?
There's no really short answer to that question, sadly. As it stands now, WPF
is accessible using UI Automation. Sadly, however, screen reader vendors
haven't added access to UI Automation, for reasons of which I'm not entirely
certain, though I expect it has something to do with their reluctance to write
part of their product in managed code (I'm not entirely certain what
performance hits they would encounter there). There is an unmanaged UI
Automation API, but documentation is minimal at best, and Microsoft strongly
advises using the managed API. What I want to know, and perhaps someone more
wise in the ways of screen reader development than I can provide an answer
here, is why the vendors don't write potential UI Automation handlers in
managed C++, which is a recommended way of mixing managed and unmanaged code in
the same application (and I expect they're using C++ for at least part of their
development as it stands).
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Thursday, February 21, 2008 2:34 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Is WPF Accessable?
Hi Punit:
Don't know, still trying to find a set of instalation instructions for VS 2008
Pro to set up an installation plan.
Rick USA
----- Original Message -----
From: Punit Diwan<mailto:punitdiwan@xxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, February 21, 2008 10:33 AM
Subject: Is WPF Accessable?
Dear Members,
We all are aware that Microsoft .NET 3.0 and later comes loaded with WPF
application development functionality. Now VS 2008, every can easily develop
WPF enabled applications.
I want to ask is it possible to develop WPF applications for we people? I
tried Linq and it seems accessable to me. Did any one tried WPF application
development using designer.
I assume once we develop WPF enabled app, we will have to use UI Automation
to make it acessable as recommended by Microsoft. Waiting for your comments.
Thanks
Punit Diwan
Other related posts:
