[jawsscripts] Re: advantages of object oriented over procedural API, plus Gw Fs Scripting methodology question.

  • From: Victor Tsaran <vtsaran@xxxxxxxxx>
  • To: Doug Lee <doug.lee@xxxxxxxxxxxxxxxx>, jawsscripts@xxxxxxxxxxxxx
  • Date: Mon, 04 Aug 2008 09:04:50 -0700

Hi Doug,
Doug Lee wrote:
> I don't understand the comment about
> VBScript not promoting open source access to assistive technology
> though.  Not only are the VBScript scripts so far written presented
> in source form, but VBScript is only one choice of several at the
> disposal of scripters for Window-Eyes.

Well, for one Window-eyes allows you to protect your scripts with some 
sort of secure certificates which, I believe, means you can hide them 
from prying eyes. I am sure that Section 508 scripters were considered 
as GW Micro badly needs to compete with JAWS in that arena.

Yes, you can use other languages with Window-eyes but, for instance, to 
use Python or PERL will require you install respective interpreters on 
the user's machine. You see where I am going...


> This is largely why I started writing code in jsl files,

I use several JSL files in JSonar scripts, www.jsonar.org, This helps 
modularize the code a bit. The biggest hurtle for me, however, is the 
conflict between names of event functions, like you can't have two 
KeyPressedEvent ones. Surely, you can somewhat get around this by naming 
those events something different but then the initial calls will still 
have to come from the main .jss file which defeats the purpose of the 
modular approach.

> On Sun, Aug 03, 2008 at 11:44:47AM -0700, Victor Tsaran wrote:
> Not to start a flame war here, but couple of points from myself.
> 1. Window-eyes opted to use proprietary technology, such as VBScript
> which, in my view, does not at all promote open source access to
> assistive technology.
> 2. JAWS scripting language isn't that bad, but it has two major
> pitfalls: we have to rely on FS to maintain it and it lacks some very
> basic data types, like floats and arrays. GW Micro did a smart thing by
> taking the burden of script maintainance off their shoulders.
> Object-oriented programming is great for larger projects but for what
> most people would use scripting language, it is probably irrelevant.
>
> Anyways, just my two cents.
> V
>
> Geoff Chapman wrote:
>> Regarding Jamal's post of last week concerning some of the advantages he 
>> currently saw and listed
>> with the current window eyes Scripting implementation over the Fs current 
>> offering, I have a question from another scripter not onlist to ask here, 
>> plus one of my own.
>> First my friend's question:
>>
>> Aside from just being yet another way to think about the
>> problem at hand, what is the true advantage of object-oriented approaches in 
>> this environment?  In other words, what can you do in an object-oriented 
>> system, that you can not do procedurally.
>>
>> And, now for my question:
>>
>> Jamal, once again thinking of both scripting approaches as you know them, 
>> and as they stand right now, would you care to comment as to whether, in 
>> your view, the scripting model that fs has in place with jaws right now,
>> holds, any, current pluses/a dvantages at all right now, either of tightness 
>> of integration or procedurally,
>> over the current gw model?
>> with all it's caveats?
>> Thanks very much.
>>
>> geoff c.
>>
>>
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
>
> __________?
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>

__________ 
View the list's information and change your settings at 
//www.freelists.org/list/jawsscripts

Other related posts:

  1. Home
  2. jawsscripts
  3. Archive
  4. 08-2008