Correction: where I wrote "Index" I should have written "Item." Note to
self: consume caffeine, THEN post to mailing list.
On 3/22/2011 8:11 AM, Ron Parker wrote:
You need to implement IDispatch. That is, it should be a COM
Automation compatible object. Note that Automation has other specific
requirements for collection objects (_NewEnum and Index) and objects
that have events (IConnectionPointContainer.) Basically, if it's an
object you could give to an ActiveScript client through some other
mechanism, it's an object you can expose as a shared object. MSDN has
some pretty good documentation on implementing IDispatch in C++, or
you can expand on the IDispatch implementations used by the event
handler in our C++ sample code. If you're using .net, it might do a
lot of the heavy lifting for you.
In addition to the standard Automation requirements, you should
implement IProvideClassInfo if you have events or if you want to make
enumerations from your type library available to scripts through our
Script.LoadClassInformation method.
On 3/21/2011 10:55 PM, Sean Farrow wrote:
Hi Doug:
When implementing a shared object, do I need to implement a specific
interface---I carn't seem to find any docs!
Any help appreciated.
Regards
Sean.
*From:*Doug Geoffray [mailto:[email protected]]
*Sent:* 22 March 2011 00:23
*To:* [email protected]
*Subject:* Re: Window-Eyes 7.5 sdk, 64-bit machines and shared objects
Chip,
You can certainly do what you said but yes, you can also use
SharedObjects.Register from any script you create. It doesn't matter
who creates the shared object.
Doug
On 3/21/2011 6:43 PM, Chip Orange wrote:
Hi Doug,
re your answer on shared objects: you didn't mean you could create
something which is part of the sharedobjects() structure used by
VBScript and JScripts apps right? You mean you could simply create a
COM object, which could be used by any and all apps?
thanks.
Chip
------------------------------------------------------------------------
*From:*Doug Geoffray [mailto:[email protected]]
*Sent:* Monday, March 21, 2011 4:37 PM
*To:* [email protected] <mailto:[email protected]>
*Cc:* Sean Farrow
*Subject:* Re: Window-Eyes 7.5 sdk, 64-bit machines and shared objects
Sean,
The 7.5 SDK is now live. You can download it along with the older
ones at:
https://www.gwmicro.com/App_Central/Developers/
Regarding your 32/64 bit install question, Window-Eyes simply copies
in the files from your .wepm and does the necessary associations.
The install of a .wepm doesn't do anything about if this OS or this
bit level. Of course you can do whatever you want with your script.
So you can include a startup global script that simply determines
whatever it is you are interested in and then deletes or runs or
renames or whatever you want.
As for shared objects, sure you can create a shared object from any
language that supports COM automation. Meaning any scripting
language or full programming language that supports the Window-Eyes
object model.
Doug
On 3/20/2011 12:56 PM, Sean Farrow wrote:
Hi:
Ok one message with a few queries:
Do we have a release date for the sdk for window-eyes 7.5 for writing
external hosted scripts/connecting other applications to we?
If I'm writing hosted scripts (c++) for 64 bit machines, does
window-eyes have a mechanism for installing certain files from a
package for 64-bit and certain files for 32-bit?
And finally, is it possible to implement a shared object in c++/an
external language?
Regards
Sean.
