[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 13:17:19 -0700


>> Even this is very complicated. You see, an msi file is a database. There
>> are no loops or anything like this we could use to go over all installed
>> JAWS versions.
>> And of course, there's also the versioning: msi keeps track of all
>> versions it installs so it can properly uninstall everything again, or
>> repair an installation. But to do that, every file that it installs can
>> only have one single destination.
>> We would have to write a custom script which the msi can execute to do
>> such an installation.
>>>> 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.
> lets start with totally silent installation - in case if we find JAWS
> installation we install scripts to the versions found silently and compile
> them - in case we do not we simply install nothing. The only hard thing
> here
> is that we shall need to test the versions of JAWS - we can walk through
> this as to create three copies of these files in the installer any of
> which
> will be installed in the exact destination depending on JAWS version -
> since
> the scripts are rather small in size - we can do such a thing I believe.
> The
> other hard thing here is that we shall need to recompile them everytime we
> are installing them - each copy with its own compiler - because the
> compiler
> changes from one version of JAWS to another. WWe need to recompile these
> scripts already in place because JAWS can be of different minor versions
> like 9.0.157 or 9.0.358 and these versions are located in the same folder
> and can not work at the same time, but one user can use the first one and
> another can use the second one - this is the reason for recompiling the
> scripts in place.

Quite forgot about one more hard point here - we need to install the scripts
in the exact language folder at the very end of the path depending on the
current language of the system.

For example if you are using the English version of JAWS you will need to
have all the scripts in the folder like: %userprofile%\Application
Data\Freedom Scientific\JAWS\9.0\Settings\ENU and if you are using the
russian version in the Russian system - %userprofile%\Application
Data\Freedom Scientific\JAWS\9.0\Settings\RUS and so on - specific for every
version of the language. Additionally the language of the system may differ
from the language of JAWS and in this case the installation should happen to
the English folder that is the default if the appropriate language folder is

In general the algorithm is the following:
1. Take the system language abbreviation.
2. Check if the appropriate folder exists at the user profile.
3. If it exists copy there and compile.
4. If not copy to the ENU folder and recompile.

To be honest a real rule is a bit more complicated but using the one
provided will suite in 99% of the installations and if the user is so clever
that he is 1% of the cases - let him install manually - I believe we can
place a zip archive on your site for those who are so clever people that can
install manually.

Thank you.



To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-03 22:17:19 CEST

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