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