Re: WindowEyes Getting Script Language

  • From: "Richard Thomas" <rthomas@xxxxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Sun, 10 Feb 2008 20:12:43 -0500

Hi:
I am waiting until I see the Interface.  Researching has led me in too many 
directions, interop as an example versus com wrappers and interface and 
overrides of DLL elements and phew!  I think I'll wait for the movie for now, 
grin.
Oh Yah, I almost forgot vb.net, vbScript, JScript, Java, CSharp, C, C++, PHP?, 
Python and a few others, some  which I've taken a quick overview concerning Com 
Objects.  Yah, I'll wait just a little longer I think.  By the way, I hope you 
are around the lists when this thing kicks off, sounds like you have a running 
start.
Rick USA
  ----- Original Message ----- 
  From: Chris Meredith 
  To: programmingblind@xxxxxxxxxxxxx 
  Sent: Sunday, February 10, 2008 3:18 PM
  Subject: RE: WindowEyes Getting Script Language


  What also might help with searches is expanding the acronym to "Component 
Object Model"--though I also agree that deciding what language to work with, 
then figuring out how to talk to COM in that language, is your best approach.  
To that end, I wonder if GW Micro will ship primary interop assemblies for us 
.NET folks, or whether we'll need to fall back on importing typelibs.

   

  -C-

   

  From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Macarty, Jay {PBSG}
  Sent: Sunday, February 03, 2008 9:59 PM
  To: programmingblind@xxxxxxxxxxxxx
  Subject: RE: WindowEyes Getting Script Language

   

  Rick,

  I agree with the suggested refinements to get better results from your Google 
searches on the topic. Most books will also suggest you check out the COM 
automation info on the Microsoft website but my experience with successfully 
tracking down info by searching Microsoft has been somewhat limited unless I 
had a starting point URL. I am a member of O'Reilly's Safari online book 
service and that is where I get most of my reference material. 

   

  As has been suggested, it might be easier to select a language and then try 
tracking down info on COM interfaces for that language. I found a number of 
references in the C# books I got from Jamal regarding using COM with .net. 

   

  If you are comfortable with vBScript or VBA, you might try searching for a 
phrase like using COM automation with VBScript and see what that turns up.

   

  Hope this helps. 

   

     


----------------------------------------------------------------------------

    From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
    Sent: Saturday, February 02, 2008 7:47 AM
    To: programmingblind@xxxxxxxxxxxxx
    Subject: Re: WindowEyes Getting Script Language

    Hi JP:

    Any suggested readings on very basics of Comm Programming?

    I'm having Google mess mixing Comm up with Communications.  Any Keywords, 
W3c Keywords or url's that might help me get started setting up homework?

      Also, if you have any tutorial url's could you let me know?

      I'm trying to find out how to get started by Googling for now.

      Rich; Farmington Mich. USA

      From: Macarty, Jay {PBSG} 

      To: programmingblind@xxxxxxxxxxxxx 

      Sent: Saturday, February 02, 2008 4:06 PM

      Subject: RE: WindowEyes Getting Script Language

       

      Rick,

      I agree that this sounds promising. I just finished reading the 
introduction to Window-Eyes scripting published by GW. Exposing Window-Eyes 
objects through COM and letting the script writer choose the language they are 
comfortable with certainly adds some flexibility. Of course it carries the 
responsibility of being aware of your audience if you are writing scripts you 
wish to share. I could probably write some nice scripts in ruby or AutoIt (and 
will probably do so for my own use) but for sharing, I'd want to make sure the 
script was written in a language such as VBScript or JScript which I could 
expect anyone to have installed. As for your question about .net managed code, 
I have written other C# programs which accessed COM objects and the intro from 
GW says it will be accessible from .net. 

       

      I think this was a very interesting design approach by GW Micro and will 
be anxious to see how it pans out. Throwing out a scripting framework which 
lets one use things like VBA, VBScript, JScript, and so on certainly opens the 
door for the rapid growth of user written and contributed scripts. 

       

         


------------------------------------------------------------------------

        From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
        Sent: Friday, February 01, 2008 7:18 AM
        To: programmingblind@xxxxxxxxxxxxx
        Subject: WindowEyes Getting Script Language

        Hi Gang:

        WindowEyes is getting a Scripting Language, finally!  OK, so they say 
it will use Com Automation and various languages can be used with the default 
language VB Script.

        First, I know some of you are really good with such thingys as Com 
Automation having done accessibility work.  Is there some good starting points 
on learning to write scripts, or they say we can use compiled programs like 
c++, and Com Automation?

        What about the Managed Code of Vb.net?

        I have always used Windoweyes but it needed some fixes in applications 
like Visual Studio and some Internet Controls weren't accessible, oh ya, java 
script sometimes gave it fits.

        I'm kind of excited.

        Rick Farmington Mich. USA

         

         

         

Other related posts: