FreeLists / ossrp-control / [ossrp-control] Re: The Longhorn Screen Reader Idea

["David Lant" <david.lant1@xxxxxxxxxxxxxx>]

Hi Will,

Also, as a purely speculative option for later requirements, by using =
the
.NET framework as the basis for the project, it may be possible to work =
with
other open source projects like Mono.NET to see if the project could be
ported to work on Linux and UNIX systems too.  It need not be an initial
priority, but it's a door that might be worth keeping ajar.

All the best,

David


-----Original Message-----
From: ossrp-control-bounce@xxxxxxxxxxxxx
[mailto:ossrp-control-bounce@xxxxxxxxxxxxx] On Behalf Of Will Pearson
Sent: 24 April 2005 12:08
To: ossrp-control@xxxxxxxxxxxxx
Subject: [ossrp-control] Re: The Longhorn Screen Reader Idea


Tink,

The idea has always been to use the various languages of the .Net =
Framework.

This would allow people to work in any of the four .Net based languages =
(C#,

VB, C++ .Net, J#) and have their components work with the other =
components=20
that have been written.

Originally, we just thought about a component based architecture for =
ease of

upgrading.  At the moment, you have to await a big monolithic file being =

released to upgrade a screen reader, but a component based architecture=20
would mean that a system, similar to Windows Update, Symantec's Live =
Update,

etc. could be used, and it's likely this could be made transparent to =
the=20
user should they desire it.

However, with all the talk of different versions of Windows, both the =
.Net=20
Framework and a component architecture seem useful.  A couple of off the =

cuff thoughts...  Whilst WinFX, the .Net Framework for Longhorn is =
different

to even v2.0 of the .Net Framework, there's likely to be some overlap.  =
So,=20
in order to modify a screen reader to work on earlier versions of =
Windows=20
all someone would need to do is to replace the components that didn't =
work=20
on earlier versions of the .Net Framework.  V2.0 of the .Net Framework=20
should work on Windows 98SE and above.  So, if the architecture is =
right,=20
you may be able to get a screen reader that works on earlier versions of =

Windows, although a lot of the functionality afforded by the design and=20
features of Longhorn won't be available in earlier versions of Windows.=20
I'll have to give it some thought as to whether this could be =
architected in

such a way.

Will
----- Original Message -----=20
From: "Tink Watson" <tink@xxxxxxxxxx>
To: <ossrp-control@xxxxxxxxxxxxx>
Sent: Saturday, April 23, 2005 10:18 PM
Subject: [ossrp-control] Re: The Longhorn Screen Reader Idea


> Will,
>
>    Good to see the project gaining momentum!
>
>    Just as a matter of curiosity, what do you anticipate the Longhorn=20
> Screen Reader (LSR?) will be written in?
>
>    I believe that Rick's suggestion of working on a modular basis is
> likely
> to be an effective methodology for building this. It could certainly
> maximise on the collected ability of people willing and able to work =
on=20
> the
> project.
>
>    Incidentally, returning to an earlier point, I almost hate to ask,=20
> but can we come up with a shorthand or working title for the Longhorn=20
> screen reader? It's an awful lot of typing!
>
> Tink.
>
> ----- Original Message -----
> From: "Will Pearson" <will-pearson@xxxxxxxxxxxxx>
> To: <ossrp-control@xxxxxxxxxxxxx>
> Sent: Saturday, April 23, 2005 8:07 PM
> Subject: [ossrp-control] The Longhorn Screen Reader Idea<SNIPPED>
>
>
>=20