>>>> Ok, then I suggest the following - creating the special branch for me
>>>> the project and lets say call it accessability. Inside this branch
>>>> will be folders for each ScreenReader that I shall support and I shall
>>>> the scripts for several screen readers under this folder and develop
>>>> increasing the accessability of TSVN for some of the screen readers.
>>>> opinion on this?
>>> I don't think we need a special branch for this. Just a new folder under
>>> our 'contrib' folder. That's where such scripts belong anyway.
>>> If you create (or already have one) a tigris.org account, I can set you
>>> up with commit access to our repository so you can add and commit these
>>> scripts yourself. Would that be ok?
>> Sure, I shall create an account and send you information on it that is
Oops, there uis a graphical capture that can not be resolved by me - hope
someone will help me to register there.
>> needed to - login most likely - or something else is needed? I was using
>> Assembla for my projects before, so I do not think this should be
>> As soon as the scripts will be at least somehow usable we shall discuss
>> to implement conditional install of them in the appropriate folder of the
>> screenreader - I am now studying WIX for my own projects installations so
>> believe it will not be dificult to add the installation in case of the
>> screenreader XXX or screenreader YYY is found in the registry.
> I suggest you create a new folder named "screenreaders" under
> /src/contrib and put all your files there. You can put your own folder
> structure under that folder, just as you like.
Sure, but the installer will need to check if the screen reader is installed
and if so - to place the resulting scripts to the special folders - unique
for every screenreader not forgetting to ask if the user wants to install
them of course. It is not enough to place them under the TSVN folder - a
tradition in screen reader developing is to place the scripts to the folders
that are specially designed for that - for example into
Scientific\JAWS\VersionNumber\Settings\enu\ in case fof JAWS - the most
popular screen reader now they will not work anywhere else escept this
folder - and the task of the installer is to place them in this folder while
installing - I believe that the best way here is to develop the small part
of WIX installation procedure for me and you shall call it if the
appropriate screenreader is installed while installing the TSVN. This will
be discussed later when there will be what to install I believe in details
>> Ok, I shall install and try the last one I shall find.
> You can find them here:
> for win32, it's here:
> and for x64 it's here:
> The 'full' folder contains a full build, including all language packs.
> It is built twice a week.
> the 'small' folder only contains the msi installer, debug symbols and
> the svn client binaries, but no language packs. It is built 5 times a
> week (on those days the full build is not built).
Thank you for direct links - I was nearly going to search for them and such
a gift as direct links is great!
>>> But I found another way. I've implemented a callback annotation server.
>>> In r17946, the log dialog now fills in the help string of subitems that
>>> are already merged (the ones shown in gray).
>> Does this mean that I shall be able to take this information from the
>> accHelp property?
> Yes, if it works as I think it does.
> I've tested it with the inspect.exe tool which comes with the windows
> SDK, so it should work with your screen reader too.
Ok, I am going to install the latest nighty build right now and check this -
I need to make some tweak merge right now and if it works this will help me
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-12 21:44:05 CET