Other may have better ideas, but mine is this: Make a wsf that groups all your support source into a single object, and just keep the master code in the actual script module. Then access your support code as you would any other shared object in a WE script. This approach lets you build a library and frees your individual scripts from clutter, though admittedly it's not quite as convenient as being able to include specific library modules in specific scripting projects. Alternatively, if your code library nicely breaks down into a few functional areas, you could make each its own shared object. This is probably more along the lines of the GW scripting philosophy, because it eases sharing of features on demand. It works well when the features you've coded apply across several projects, but the first approach will probably work better for code that is massive but specific to one project.
On Mon, Sep 08, 2008 at 07:22:13AM +0100, Tim Burgess wrote: OK, so there's no method of modularising the code for a large amount of source? Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -----Original Message----- From: Ron Parker [mailto:[EMAIL PROTECTED] Sent: 08 September 2008 01:45 To: [email protected] Subject: Re: .VBF files and WE scripts Aaron, you're a bit wrong here. We specifically look for encrypted scripts in wsf files, but all other wsf files get passed to Windows Script Host. They'll work with WE, but only in the way that any external program will. That is, they'll have to create a WindowEyes.Application object and identify themselves as a script, and they won't have access to any of the methods of the Script object. Aaron Smith wrote: > Tim, > > Are you referring to WSF files? If so, then, yes, you can use those. > You'll note the extension to an encrypted script file ends in .WSF. > VBF files, from what I've gathered, are Outlook Free/Busy files. > > You might, however, investigate the Shared Objects feature of > Window-Eyes script. This is a built-in method of being able to share > objects across scripts. In fact, it's the main point of the GW Toolkit > script. > > Aaron > > Tim Burgess wrote: >> Hi, >> >> Is the use of .vbf files supported with Window Eyes? I'd like to >> modularise a large amount of code, if possible. >> Best wishes. >> >> Tim Burgess >> Raised Bar Ltd >> PO Box 4442 >> Atherstone >> Warwickshire >> CV9 9AT >> >> Phone: +44 (0)1827 719822 >> Email: [EMAIL PROTECTED] >> Web: http://www.raisedbar.net >> >> Don't forget to vote for improved access to music and music >> technology at >> >> http://www.raisedbar.net/petition.htm >> >> > -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[EMAIL PROTECTED] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
