Hi Guys:
Let me pick up the groups questions all at once.
You can use a dll in any programming language so long as the dll is
compatible.
I am not a com guy by any measure so Ill leave it to others to get into the
nuts and bolts in another thread dedicated to this since you will likely get
allot of postings not related to the subject of this thread as you walk
through the solution to your question.
Second, C++ is a low-level language and I am not sure if best used in the
Microsoft IDE Managed Code Environment - Havent touched a low-level language
like c++ or Assembler etc in about 30 years now.
But it is popular for working on screen readers like WE and others.
In the Managed environment of the MS IDE it might be more powerful because
of built in features related to the .net Framework- don't know.
Finally, C# is almost identical to vb.net in features.
Remember both are based on the same framework objects and are translated by
common routines into IML so they are very, very similar in features.
There are a few differences but nothing that screams c# over vb.net or
vb.net over c#.
The real trick is not worrying about the language you pic in the .net
environment, that is usually just using diferent words to do the same
things, but learning the .net framework and the namespaces and classes and
objects methods, properties and events you use to get the real power of the
IDE Environment.
Also, you can write your methods etc in vb.net or c# and run them through a
free online translator and it will convert one language to the other with
very good results - I did this a few times and found I only had to tweak a
little of the code if at all to get the converted code to work.
I have not heard of any C++ "External Scripts" being put up on the GW
Scripting Site nor any documentation related to C++ Scripts.
Aaron and otherold pros are good at this stuff but Ive not done anything
with c++ in too many years to make my experience viable and relevant today.
I just don't know about any well supported "External" scripting platform to
begin to compare to the VbSCript sample code base and documentation when it
comes to the WE Object Model or even using UIA events in a project.
Since Aaron has said they are not concerned with VbSCripts longevity I am
guessing they will keep developing in VbScript for the forseeable future.
That means any development done outside the current documentation and code
base of sample scripts will require allot of independent learning and
experimentation.
The guys at GW are pretty good at trying to help out but if they are not
really good at the language you are trying to learn they might not be able
to best help with dificult technical questions about the interface or other
non-we related com operations and complexities while slogging through the
really complex world of UIA and other accessibility technicals they are
being confronted with today.
So, is it worth learning to create "External" scripts?
I just dont know.
VbScript is great for beginners and Aaron says will be around for years to
come and likely right.
It has many limitations and is slated,according to something I read from
Microsoft, to go away someday.
To become real scripting pros I do think you need to get away from VbSCript
and into a power language of some sort either using the WE COM Model or
something else.
Lets see how much traffic this thread gets this week to see who is
interested in thissubject going forward or if a spin-off of interest crops
up.
Some day there might be a WindowEyes Script Developers Website built by the
User Community dedicated to External Scripting in one particular language to
build a code base and related documentation - who knows.
Again lets see who has an interest in such heavier technicals since most of
us are light and lighter in the com and UIA related pants all be it some are
heavy in the use of the WE Object Model.
Rick USA
