RE: VB.net And Windoweyes Scripting
- From: "katherine Moss" <plymouthroamer285@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Tue, 22 Jun 2010 22:00:55 -0400
My only problem is knowing how to shut off UTF8 in Visual Studio. I don't
have a problem with all the curly braces, it's more the automatic double
quotes I have issues with. I heard that shutting off UTF8 will solve that
problem. Does anyone here know how to actually do that? Thanks.
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of RicksPlace
Sent: Tuesday, June 22, 2010 5:37 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: VB.net And Windoweyes Scripting
Well Katherine, since it sounds like you already have a .net programming
background you can develop in any of the languages. I have seen little
diference in the capabilities of Vb.net and C#. C++ on the other hand is a
whole other animal. If you try and use c++ in the .net environment you can
use both managed code features and write for non managed features. If you
use c++ outside of the .net environment I don't think you can use the
managed features of the .net frameworks without jumping through some really
complicated hoops. For games I have seen articles by folks who have used all
of the languages. C++ gives you the most control over your application while
C# and Vb.net are pretty much the same with diferent syntax and typing
restrictions. I hate having to mess with all the curly braces in C# as well
as some other things I find annoying. I have seen this question asked on
list a hundred times and there is no one good answer. If you are comfortable
in the .net environment stay there and become an expert in one language. It
is not so much which language you use but how well you can use the language.
Most modern languages will allow you to do heavy work. The trick is to pick
a language and become really good at using it. If you can solve a problem
without looking up things you will have more fun than if you have to look up
every statement while coding; Or, look up what objects, functions or
properties or events to use to do something and then how to use them with
parameters, enumerations and correct syntax. If you like .net and have
friends who use it stay with it and just start using either C# or C++ if
that is your decission. Just get good at what you do and you will be able to
do just about anything you can think of in either language, or vb.net for
that matter. One final note, if most of your friends program in one
language you might have more fun learning that language so you have things
to share with them. Well, that's my story and I'm sticking to it - at least
for the moment grin.
Rick USA
----- Original Message -----
From: "katherine Moss" <plymouthroamer285@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Tuesday, June 22, 2010 4:40 PM
Subject: RE: VB.net And Windoweyes Scripting
> Speaking of .net languages, remember in my last email to you that I told
> you
> that I'm drawn to them? Well, I constantly have friends reminding me that
> I
> should focus on other languages too. Take for example, my eventual desire
> to learn C#. I in no way want to be a programmer for a career, but rather
> for enjoyment. If so, am I good having C# and JAWS script under my belt
> to
> be able to create things like games, and in turn to help the blind
> community
> succeed with a few extra scripts added in to the mix? Or is it essential
> in
> this world that I learn something like C++ even though C# has it's roots
> there? Any input would be good.
>
> Thanks guys,
> Katherine
>
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
> Sent: Tuesday, June 22, 2010 8:30 AM
> To: programmingblind@xxxxxxxxxxxxx
> Cc: RicksPlace
> Subject: Re: VB.net And Windoweyes Scripting
>
> Yes, the VB.NET fruit basket on Script Central is my latest. As far as
> I remember, the only necessary COM reference in VS would be to
> WinEyes.dll. VS should then automatically generate an Interop assembly,
> a "COM Callable Wrapper." There some deployment related issues I can
> touch on later if you decide to distribute your VB.NET-based Window-Eyes
> script.
>
> Jamal
>
> On 6/21/2010 11:32 AM, RicksPlace wrote:
>> Hi Jamal et al:
>> First, Jamal, is your version of the Fruit Basket, v1.6, on the
>> Windoweyes Download Center the most current version?
>> I will use your Script Installer to install it next if you give me the
>> go ahead.
>> Here are the steps I have gone through so far to learn how to make
>> VB.net 2008 work as a Script Editor for the Windoweyes Com interface.
>> A finished tutorial might be totally diferent since it will likely have
>> a diferent example.
>> But here are the steps I am doing to get started if anyone is interested
>> in following along or wants to help me out.
>> BeginSteps:
>> Step01:
>> Download and install We V7.2
>> Done:
>> Step02:
>> Navigate to:
>> https://www.gwmicro.com/Script_Central/Developers/#mainHeadingTitle
>> Cursor to:
>> Window-Eyes Scripting SDK
>> Window-Eyes 7.1 Scripting SDK
>> Window-Eyes 7.0/7.01/7.02 Scripting SDK
>> Click:
>> Window-Eyes 7.0/7.01/7.02 Scripting SDK
>> The following Page came up:
>>
>
https://www.gwmicro.com/Script_Central/Developers/SDK/?ver=70#mainHeadingTit
> le
>>
>> Cursor to:
>> Window-Eyes Scripting SDK
>> The Window-Eyes Script Development Kit contains support files that are
>> needed to
>> develop external scripts in various popular languages. These include the
>> object model
>> interface definitions, the type library, and various C-language support
>> files generated
>> from the interface definitions.
>> The SDK also includes VBGetRef.dll, which is necessary to use Visual
>> Basic to write
>> external scripts. VBGetRef is provided for development purposes; it is
>> also included
>> with the
>> GW Toolkit
>> script, so it is neither necessary nor recommended to include it with
>> your script
>> package.
>> END-USER LICENSE AGREEMENT FOR GW MICRO SOFTWARE
>> ...
>> Check:
>> I agree to the EULA for the Window-Eyes Software Development Kit
>> Then clicked:
>> Download the Window-Eyes Scripting SDK button
>> we70sdk.zip was downloaded:
>> BeginUnzippedContents:
>> comevent.h
>> wineyes.h
>> gwmver.h
>> license.txt
>> vbgetref.dll
>> wineyes.h
>> wineyes.idl
>> wineyes.tlb
>> wineyes_i.c
>> EndUnzippedContents:
>> Done:
>> Step03
>> Navigate back to:
>> https://www.gwmicro.com/Script_Central/Developers/#mainHeadingTitle
>> Cursor to:
>> Window-Eyes External Script Examples
>> Visual Basic .NET (for Window-Eyes 7.1 or greater)
>> Visual C# (C-Sharp) (for Window-Eyes 7.1 or greater)
>> Visual Basic 6
>> Visual C++ 2005/2008
>> Window-Eyes External Stand-alone Application Examples
>> Visual C++ 2008
>> Click:
>> Visual Basic .NET (for Window-Eyes 7.1 or greater)
>> The Following Page came up:
>> https://www.gwmicro.com/Script_Central/Developers/VB.NET/
>> Cursor to:
>> External Visual Basic .NET Script Example
>> This example demonstrates how to connect to the Window-Eyes script
>> manager from a
>> VB.NET application, how to register and respond to a hotkey, and how to
>> work with
>> various events.
>> File Details:
>> Filename: vbnet-example.zip
>> Date: June 30, 2009 2:14:00 pm
>> Size: 129.8KB
>> Download Now
>> This example requires the
>> GW Toolkit
>> script.
>> Click:
>> Download Now
>> vbnet-example.zip was downloaded
>> BeginUnzippedContent:
>> vbnet-example folder at level 1
>> vbnet-example SubFolder at level 2
>> vbnet-example SubSubFolder at level 3
>> Scripting.dll at level 3
>> vbnet-example.sln at level 3
>> vbnet-example.xml at level 3
>> windoweyes.dll at level 3
>> EndUnzippedContent:
>> Done:
>> EndSteps:
>> Rick USA
>>
>>
>>
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 5219 (20100622) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 5219 (20100622) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5220 (20100623) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5220 (20100623) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
