[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Several things to discuss in terms of accessability.

From: Serge Tumanyan <tumanyan_at_mail.ru>
Date: Mon, 3 May 2010 23:49:04 -0700

Stefan,

> The nightly build with these changes won't be online for at least five
> hours. The build starts at 24:00 GMT+2.

Ok, I shall see it tomorrow here.

>> Ok, here is the way to find out that JAWS is installed and what version
>> is
>> used:
>> The registry key:
>> HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS
>> contains all versions of JAWS that are located on this machine, that is
>> the
>> subkeys: 9.0, 10.0, 11.0 mean that the versions 9.0, 10.0, 11.0 are
>> installed side by side - it is a very often practice in JAWS
>> installations -
>> a lot of people use a couple versions of JAWS at the same time for
>> different
>> reasons.
>>
>> If you find any of these keys in the path I have pointed in the registry,
>> you can use %UserProfile%\Application data\Freedom
>> Scientific\JAWS\^Version^\Settings\^Language^ folder to install the
>> scripts.
>>
>> Here ^version^ is full version of JAWS, like 9.0, 10.0 or 11.0 and it
>> corresponds directly to the registry key that points version of JAWS.
>> ^Language^ is three letter abbreviation like ENU for English united
>> states,
>> RUS - for Russian or FRC - French Canada - hopefull you can get these
>> standard abbreviations in installer scripts.
>>
>> Since several versions of JAWS can be installed side by side at the same
>> partition in different folders - they will work independantly we need to
>> provide some kind of a listview with the found versions and checkboxes
>> where
>> to install the scripts - fortunately all the installed versions can be
>> found
>> while browsing through the registry - every has its own key.
>
> That won't be easy. WiX and msi don't provide easy ways to fill such
> list controls. And of course we would have to first create a separate
> msi dialog for that, which also isn't easy to do.

Ok, let us install the scripts to all the versions that are found in the
registry without asking. I believe that this will be quite fine. If the user
checks the checkbox the scripts are installed in all found versions, and if
the checkbox is unselected they are not installed. Quite reasonable.

We can enhance this in the future if needed.

>> Now when we know all the folders where JAWS scripts will be installed we
>> can
>> copy them in these folders and need to compile them. For that goal every
>> registry key contains a 'Target' value containing the path to the folder
>> where JAWS binaries are located and you need to start the unique scompile
>> binary for every version of JAWS with the following command line:
>> scompile
>> "%userProfile%\application data\freedom
>> scientific\jaws\^version^\Settings\^Language^\TortoiseProc.jss.
>>
>> That's all.
>>
>>> I think it would be best to add another "Feature" which is shown in the
>>> installer page, where the user can now choose to install additional icon
>>> sets and spell checker modules.
>>> And if you're ok with it, I'd like to have the JAWS script feature
>>> disabled by default, so that only users who really need it get it
>>> installed.
>>
>> I believe that you need to disable the feature by default if you have not
>> found JAWS versions 9.0, 10.0 and 11.0 on the machine and enable it by
>> default in case you have found these versions - most likely the JAWS
>> users
>> of these supported versions will like to install it and if they do not
>> they
>> can uncheck the checkbox.
>>
>> I also suggest to add a Browse button for those users taht do not have
>> the
>> versions of JAWS supported and want to try if the scripts work for
>> earlier
>> versions. In addition, the user can also have a flash version of JAWS on
>> his
>> machine and in this case there is no registry keys and the settings can
>> be
>> located whenever the user wants them to be located. For such clever users
>> the Browse button will be fine and no compilation needed - if they are so
>> non-standard - let them compile the scripts themselves.
>
> Remember that we're using WiX and msi for our installer. Doing such
> complicated tasks is very complicated and requires a lot of work. And I
> mean a *lot*.
>
> Maybe it would be better if we just search for JAWS installations and
> always install the scripts automatically, without any UI.

Ok, this is a good starting point. Later we can enhance this if needed.

Will it be very hard to do the following:
1. a checkbox to install scripts.
2. Radio buttons A. Standard install, B. Custom Install.
3. If custom install selected to allow the user to select a folder to
install manually and in case of standard install install to all JAWS
versions found.

Unfortunately I am not very well familiar with WIX and MSI, so I hardly
understand what task is simple and what is not - I usually work with
different installer packages in my practice.

Thank you.

Serge.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2602028

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-03 20:49:06 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.