Hi Jonathin, The primary advantage to any .net language (as well as python, PowerShell, and some other scripting languages) is that they have access to DLL libraries, and libraries of managed code (such as the UIA libraries) which VBScript does not. You can also (theoretically) generate more sophisticated dialogs than are possible with the XML dialog facility. I say theoretically because I believe it's not really possible without sighted assistance, but this is an opinion mixed-in with these more-or-less facts.
If you aren't using my Word VBA editor, then you also have the advantage of an environment with a good code editor, an object browser, and giving your variables types and using intelli-sense, which helps enormously when you go to write code for some object model (like Window-Eyes) where you would otherwise have to remember (or look-up) hundreds, or even thousands, of properties, methods, event handler syntax, etc. This particular advantage just can't be under estimated, and that's why, as shameless as it is, I take every effort to recommend my Word VBA editor to anyone who wishes to work with VBScript (because it does give you these last advantages, if you own a copy of Word). Also, while the speed of the execution of your app is rarely a limitting issue, it can be (especially when you may have to do a great deal of string handling or extreme calculations) at times a requirement for much faster execution, and in that case you are likely to need a compiled language (a .net language). I am cautious in saying this is a hard and fast rule because often, simply choosing a better algorithym can have more of a benefit than compiling your code. You should also ask about the disadvantages; I would venture to say that something like VB.net (or any .net language) is much much more complex to learn than is VBScript; also, writing even the simplest app takes much longer, especially when you find you need to make a very minor change (it's almost instant in VBScript, but it certainly is not in a compiled language). It's this added complexity, and difficulty in developing the smallest of apps, which I believe prompted Window-Eyes to first recommend scripting languages such as VBScript and Jscript as the suggested environments for our apps. However, there are rare instances where the added power of such languages is really necessary for something in particular to be done, and if you have the time, it's really worth it to know both environments, and to be able to select which ever one fits your immediate needs. Finally, while no one here as written a very large published app (although I am in the process of doing so in VBScript), they generally become easier to do in a .net language, so it becomes more accepted that the larger the app, the more you will probably lean to a compiled language, which better supports all the complexities of very large programs. Hth, Chip -----Original Message----- From: Scripting [mailto:[email protected]] On Behalf Of Jonathan C Cohn via Scripting Sent: Sunday, April 05, 2015 1:29 PM To: Rick Thomas; Window-Eyes Scripting List Subject: Re: New Window-Eyes C# Example Now Available Are there any advantages to vb.net? I would be interested in helping you with the project though I still need to upgrade to WE 9 on my personal systems before I could be of much help. Jonathan > On Apr 4, 2015, at 05:28, Rick Thomas via Scripting <[email protected]> wrote: > > I almost forgot: The process of integrating the WindowEyes model in vb.net > is almost identical to that of doing it in C# - only the syntax of a few of > the statements is diferent but the implementation is identical if I remember > correctly. > If there are scriptors interested, serious folks I think might be able to > handle the change, I would be agreeable to working on a group scripting > project to help demo and document a real-world Vb.net script built on the > .net platform from the ground up. > I hope you will help with any problems related to com interface if any crop > up we cant handle alone and fix any problems we may encounter if any of > those crop up as well in the WE Model. > That said, I can try and pull down my old project to refresh myself on some > of the com basics - think I still can get at it, and I usually do my > homework before asking for help so help shouldn't take much time on your > part now that you have provided the basics out of the gate. > Later and this could take WindowEyes scripting to a new level including UIA > in the mix if the scriptors on list can learn to use it as their tool of > choice. > Rick USA > > > -----Original Message----- > From: Scripting > [mailto:[email protected]] On > Behalf Of Rick Thomas via Scripting > Sent: Saturday, April 4, 2015 5:15 AM > To: 'Aaron Smith'; 'Window-Eyes Scripting List' > Subject: RE: New Window-Eyes C# Example Now Available > > Hi Aaron: > That should be good news for a couple of members who were asking about > creating external scripts. > A external script created in the .net platform has direct access to not only > the WindowEyes Object Model but also directly to the UIA DOM properties and > methods. > I can help anyone of the experienced scriptors on list get setup for > accessibility - basically turn off the error window, if that works in C#, > and turn off allot of the dynamics and set all windows to be tabbed > documents. > That platform is indeed a powerhouse once they get up to speed using it and > not even on the same planet as a scripting language like VbScript from a > project design, management and the tools available for handling objects and > project structure. > Also, they can still create native scripts like VbScript in the IDE and just > use the editer and all the nice project management tools to create VbScripts > if they just want a good TextEditer with the ability to setup individual > object classes in a folder structure rather than in one giant file and have > them assembled at compile time. > Anyway, tough job learning everything but it is the next logical step in the > progress me thinks. > The alternative would be an external script in something like Python which > might also be a good choice and perhaps easier to learn for current > scripters but I have little and less experience in Python so cant speak to > that arena at all from a informed viewpoint. > Later and we shall see...Rick USA > > _______________________________________________ > Any views or opinions presented in this email are solely those of the author > and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/ofbgmail% > 40mi.rr.com. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com > > _______________________________________________ > Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. > > For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/jon.c.coh n%40gmail.com. > For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com > List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/lists3717 %40comcast.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
