View source - GWWiki

You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page:
[[Category:Scripting]]
__NOEDITSECTION__

 <Index>
 <000: Introduction>
 <010: WalkThrough - The WEScriptFramework Wizard>
 <020: Load, Attach, And First Test>
 <030 Add A String To NotePad.xml>
 <040: Create The VBScript DuplicateWarning Code >
 <050 Adding Alternative Language Support>
 <051 Create A Temporary Language Section To Modify>
 <052 Modify The LanguageCode>
 <053 Translate To Norwegian>
 <054 Test The Norwegian Language Element>
 <060 Creating The Installation Package>
 <070 Add NotePad2001 To AppCentral>
 <071 Testing The Installation>
 <Appendix A: Set Up A App Central Account>
 <Appendix B: Microsoft MSDN Language Codes>  
 </Index>

=<Content>=
==<000: Introduction>==

This is a WalkThrough of building a script to warn against opening multiple copies of the same NotePad File.
It includes: 
creating a App Central Account in Appendix A;
Steps for using the WEScriptFramework  to create an initialized  script with Windoweyes related features;
A modified version of Chip's original VBScript to produce the warning;
Create a Installation Package using the WindowEyes Package Manager.
Add the NotePad2011 App to App Central.

 </000: Introduction>

==<010: WalkThrough - The WEScriptFramework Wizard>==

Open the Wizard using
control-`
Read the first Introduction Window tab and hit Next.
Enter NotePad2011 In the Name EditBox tab and click Next.
Enter 00 in the Version EditBox tab and hit enter.
In the Description EditBox Enter:
Developed by Rick USA
Tab and click Next.
In the Script Help EditBox enter:
Functions:
1) Warn Of Attempt To Open duplicate Instances of the same Notepad File.
Development Environment:
Windows XP Professional with ServicePack 3.
NotePad Version 5.1.
Then, tab and click Next.
Leave theInclude Support For Automatic Updates unchecked, tab and click Next.
Check the  Include Enhanced Error Reporting CheckBox.
Tab and enter the same e-mail address you entered when you added the e-mail address to your App Central Profile under Extended Error Reporting.
Then Tab and click Next.
Leave IncludeScript HotKeys Unchecked, tab and click Next.
We will not add additional GWToolKit features so tab and click Next.
Enter your name for Author and you can leave the Website EditBox blank:
We dont need a copyright so, tab and click Finish.
The Save Dialog comes up:
The Save In:  ComboBox should be Default
The name should be: NotePad2011
The File Type will be vbs
Click the Save Button.
A final window comes up showing the names of the NotePad2011.vbs and the NotePad2011.xml files.
There is a button to edit these files but just tab and click the Close Button.
Now your NotePad2011.vbs file and your NotePad2011.xml files
are loaded into the WindowEyes Default Directory. 
This is where they will reside during Coding, testing and in final Production.
You are done with the Wizard.

 </010: WalkThrough - The WEScriptFramework Wizard>

==<020: Load, Attach, And First Test>==

===Process Overview===

The Script generated by the WEScriptFramework is a valid script.
It does nothing but will run without errors.
That means we can load it into AppManager as a running script and, 
attach it to the NotePad Target Application without problems.
At this time we will also pick our Text Editor of choice for this NotePad2011.vbs script.
Then we will be ready to add our  VBScript Code, test, and debug.
I like to do things in small modules which is called modular programming. It has advantages but beyond the scope of this article.

*Step01:
Open Notepad so we can attach our NotePad2011 Script to it.
Control- BackSlash to WindowEyes.
Alt to bring up the MenuBar:
Expand the AppManagement node under the Apps Menu and click appManager.
Set the RadioButton to Display Apps Program: NotePad.
Tab and click the Load Button.
You come up in aComboEditBox labeled FileName:
*Step02:
Tab Around and make sure your Default directory is selected in the  LookIn ComboBox if that is where you saved it.
Tab 2 more times  to 
a ListView also labeled Look In: 
This is a list of Scripts you can select from.
You can then hit the letter "n" to jump to the scripts starting with the letter "n".
Cursor down to find NotePad2011.vbs
Tab and NotePad2011.vbs should now be listed in the FileName ComboEditBox.
Tab and click the Open Button.
You should be returned to the AppManager and hear that NotePad2011 is running and the description you entered in the WEScriptFramework Wizard.
*Step03:
Tab to and click the Help And Options Button.
Tab and hear our  Help Text we entered in the WEScriptFramework.
tab and the CheckForUpdateNever radio button should be checked.
Tab and click About button.
You hear a little about the script like the author, version, date and a VisitWebsite button.
Note: We entered a dummy website in the WEScriptFramework so, 
this wont work until we update the Website Property in our script with a real Web Address.
Tab and click the Close Button.
You are returned to the   HelpInformation Window.
Tab and close the HelpInformation Window.
You are returned to the AppManager.
*Step04:
Tab to and click the Advanced Button.
The Advanced App Settings Window comes up.
On this window you can use the default editor or navigate to a editor of your choice and click the Assign button when you have one selected.
I clicked the FindEditor button, navigated to my VBSEdit.exe program and Clicked Open.
You are returned to the Advanced App Settings Window.
Click Close to return to the AppManager.
*Step05:
Hit I to open the editor you have chosen for NotePad2011.vbs.
Your script comes up in the editor ready to work on.
You can work on it in AppManager this way or, 
work in it outside AppManager by opening the NotePad2011.vbs file in the Editor you have selected.

 </020: Load, Attach, And First Test>

==<030 Add A String To NotePad.xml>==

We need to add a string entry into our NotePad2001.xml file to speak when a Client opens a duplicate NotePad Window.
We will give it a ID of:
DuplicateOpenFileWarning
And a value of:
File is open more than once.

*Step01:
Open Windoweyes and click on Explore UserProfile Folder under the File Menu.
In the Default Folder navigate to NotePad2011.xml.
Right Mouse click it and pick Edit.
Navigate down to the end of the Language Section Element.
You can do a find on:
</language>
On a blank line just above this statement add:
			<string id="DuplicateOpenFileWarning"><![CDATA[File is open more than once.]]></string>
Close the xml file and save your work.
You can hit enter on the NotePad2011.xml file and it should come up in your default browser.
If you get no errors it should be syntactically correct.
You can close everything up.

 </030 Add A String To NotePad.xml>

==<040: Create The VBScript DuplicateWarning Code >==

===Process Overview===

We have already attached our script. 
This means that if we get any errors they will appear when we open Notepad after Reloading our modified script.
I usually add a text file to log error messages. 
but, this is such a straight forward app we can just use a Speak command for debugging.
We will add code modularly, in small functional blocks.
Make sure each block runs and then add the next block.
We will add a speak command anyplace we want to verify something or, 
check any runtime error conditions.

*Step01:
Open NotePad.vbs in your text editor.
Navigate down past all the auto-generated code:
The last Code Block in my script is the function:
 BeginCopiedCode:
<code>
 Function MenuProc(menuObj, id)
 	MenuProc = False
 ...
 End Function
</code>
EndCopiedCode:
*Step02:
Now, after the final End Function statement,  
add the following code:
 BeginCopiedCode:
<code>
 ' BeginMainSection
 dim gDeskTopOnChildCreateEventConnection
 gDeskTopOnChildCreateEventConnection = connectEvent (  desktopWindow , "onChildCreate", "DeskTopOnChildCreateEventHandler")
 sub DeskTopOnChildCreateEventHandler(ReturnedWindowObject)
 queue "checkWin", ReturnedWindowObject
 end sub
 sub checkWin(PassedWindowObject)
 Speak "Creating A Desktop ChildWindow " &PassedWindowObject.Name 
 End Sub
</code>
 EndCopiedCode:
Close your text editor and save the changes.
Now Open a file in NotePad, then try and open another with the same file selected.
You can just open NotePad then try and open it again since the default empty document will work.
You should hear a bunch of spoken ChildWindow open messages along with  the various standard objects and text you would hear opening a NotePad file.
If you dont hear the messages double check your code.
You might also have to ReLoad the script depending on your Text Editor Assignment.
*Step02:
Navigate to the code block:
<code>
 sub checkWin(PassedWindowObject)
 Speak "Creating A Desktop ChildWindow " &PassedWindowObject.Name 
 End Sub
</code>
We will modify this sub to look like:
BeginCopiedCode:
<code>
 sub checkWin(PassedWindowObject)
 dim lWindows , lWindow
 sleep 500 ' give application half a second to initialize window
 ' We only want Overlap orMDI Child Windows. 
 if Not (PassedWindowObject.style.overlapped or   PassedWindowObject.style.MDIChild) then
 Exit sub
 End If
 ' We only want to check Created NotePad Window.
 if Not (PassedWindowObject.className = "Notepad") then
 Exit Sub
 End If
 Speak "We Have A NotePad ChildWindow Opening"
 End Sub
</code>
 EndCopiedCode:
Close your text editor.
Open NotePad then Open it again.
You should hear your message "We Have A NotePad ChildWindow Opening"
Again if you do not hear it check your code carefully.
*Step03:
Because there are times we want NotePad opened but with diferent files being edited,
we only want to warn if we attempt to open a NotePad Window with the same file in it.
We can filter all the Opened NotePad Windows checking if they match the window attempting to open as picked up in the OnChildCreate event.
Open NotePad2011.vbs in your editor.
Navigate down to the sub:
<code>
 sub checkWin(PassedWindowObject)
</code>
Remove the Speak "We Have A NotePad ChildWindow Opening" Statement.
Now, After the last line of code and just before the Exit Sub statement:
Add the following code block.
 BeginCopiedCode:
<code>
 ' We  are creating a NotePad window, check to see if it is already open.
 set lWindows = _
 windows.filterByTitle( PassedWindowObject.title ) 

 for each lWindow in lWindows
 if lWindow.handle <> PassedWindowObject.handle then
 if lWindow.className = "Notepad" then
 silence
 sleep 1000 ' pause one second after going quiet
 speak PassedWindowObject.title
 speak MyStrings(DuplicateOpenFileWarning)
 End If ' if lWindow.className = "Notepad" 
 End If ' if lWindow.handle <> PassedWindowObject.handle
 next
 ' EndMainSection
</code>
 EndCopiedCode:
Close your Editor saving your work.
Note that in the statement:
speak MyStrings(DuplicateOpenFileWarning)
We are speaking the value of the string we added to the NotePad2011.xml file.
Actually we have loaded the strings from the NotePad2011.xml file into the MyStrings Dictionary and pulling the value from there.
Open NotePad a few times with the same  file and then with a diferent file.
You should get the warning if the same file is attempted loading but not hear the warning if there is a diferent file in NotePad to be edited.

 </040: Create The DuplicateWarning Code >

==<050 Adding Alternative Language Support>==

===Overview===

We can add support for many languages in our VBScript Applications.
The way it works:
As a Application Programmer we code our initial application in our language of choice.
We store various items in our xml files related to our application including Strings and User Interface objects like Dialogs, menus etc...
So when a Client uses our Application they will normally see, hear, only the strings of text or text data related to some User Interface object.
We can translate this User Text into any Language supported by Microsoft and have our Application usable globally.
To do this we include a section in our xml file for each language we wish to support.
Inside that section we will define all the elements we will expose to a Client using our Application.
The xml Language Sections structures are identical from language to  language except for the User Interface elements.
Therefore we can copy a language section, 
translate the User Interface elements into another language and, 
paste the modified language section into our xml file and have support for another language in our application.
Below are the steps I followed to add Norwegian to my NotePad2011 xml file.

 </050 Adding Alternative Language Support>

===<051 Create A Temporary Language Section To Modify>===

====Overview====

A Language Section is refered to in xml terms as an "Element"
A "Element has an Opening xml tag and a closing xml tag. 
There may be other xml taggs nested within any outtter tag pairs.
Learning xml is beyond this article but something you might want to look into.
In our NotePad2011.xml file the opening and closing tag pair for the English Language look like:
 BeginCopiedCode:
<code>
	<language id="en-us">
 .... other nested tag pairs go here
	</language>
</code>
 EndCopiedCode:
Here is the same tag pair we would use for a Norwegian Language Element:
 BeginCopiedCode:
<code>
	<language id="no">
 .... other nested tag pairs go here
	</language>
</code>
 EndCopiedCode:
Notice the LanguageCodes "en-us" and "no" in the opening tags.
These are the Microsoft String LanguageCodes for United States English and Norwegian respectively.
These LanguageCodes tell Windoweyes to automatically use the United States Language Element if the NotePad.2011.vbs Application is opened in the United States and,
to use Norwegian if opened in Norway.

*Step01:
Open NotePad2001.xml for editing.
I just wanted to use a default text editor so:
I found NotePad2011.xml in my Windoweyes Default directory,
right mouse clicked it and selected "Edit" from the dropdown Context PopUp menu.
Note: You would be smart to make a copy of this original xml file in case things go horribly wrong and you want to restore the original version.
*Step02:
Navigate down to the English Language element and copy it to the ClipBoard.
It looks like:
 BeginCopiedCode:
<code>
	<language id="en-us">
		<menu id="my_script_menu">NotePad2011<menuitem id="menu_help" enabled="yes" shortcut="h">Help...</menuitem>
		</menu>
		<strings>
			<string id="SCRIPT_NAME"><![CDATA[NotePad2011]]></string>
			<string id="SCRIPT_VERSION"><![CDATA[00]]></string>
			<string id="SCRIPT_DESCRIPTION"><![CDATA[Developed by Rick USA.]]></string>
			<string id="SCRIPT_HELP"><![CDATA[Functions:
1) Warn Of Attempt To Open duplicate Instances of the same Notepad File.
Development Environment:
Windows XP Professional with ServicePack 3.
NotePad Version 5.1.]]></string>
			<string id="GWToolkit_Required"><![CDATA[This script requires the GW Toolkit.]]></string>
			<string id="DuplicateOpenFileWarning"><![CDATA[File is open more than once.]]></string>
		</strings>
	</language>
</code>
 EndCopiedCode:
*Step03:
Paste the Language Element into a text editor so you can work in it outside your original xml file.
This is just a safer way of making modifications.
We will paste the translated xml block back into our NotePad2011.xml file when done making changes.

 </051 Create A Temporary Language Section To Modify>

===<052 Modify The LanguageCode>===

*Step01:
Open your temporary copy of the English Language xml Element.
Navigate to and change  the LanguageCode in the Opening Tag:
From:
	<language id="en-us">
to:
	<language id="no">
Above we just changed the LanguageCode in the tag so Windoweyes will know to use this block of xml if the NotePad2001 App is opened in Norway.

 </052 Modify The LanguageCode>

===<053 Translate To Norwegian>===

Since I do not speak any secondary languages,I used Jamal's LanguageTranslate App to perform the translations from English to Norwegian.
It can be downloaded from App Central if desired.
To modify our Temporary xml Language Element:

*Step01:
Identify what to translate:
We only want to translate elements that the user will see, hear.
Looking at the above English Element, 
I copied the following text into Jamal's translator, 
then replaced each line of english text with the Norwegian translation.
The Translations are below:
BeginCopiedCode:
Original English String:
New Norwegian String:
Developed by Rick USA
Utviklet av Rick USA

Functions:
Funksjoner:
1) Warn Of Attempt To Open duplicate Instances of the same Notepad File.
1) advarer mot forsøk på å åpne doble forekomster av samme Notepad fil.
Development Environment:
Utvikling Miljø:
Windows XP Professional with ServicePack 3.
Windows XP Professional med servicepack 3.
NotePad Version 5.1.
NotePad versjon 5.1.

This script requires the GW Toolkit.
Dette skriptet krever GW Toolkit.

file is open more than once.
fil er åpen mer enn én gang.
EndCopiedCode:
My Temporary Language Element now looks like:
BeginCopiedCode:
	<language id="no">
		<menu id="my_script_menu">NotePad2011<menuitem id="menu_help" enabled="yes" shortcut="h">Help...</menuitem>
		</menu>
		<strings>
			<string id="SCRIPT_NAME"><![CDATA[NotePad2011]]></string>
			<string id="SCRIPT_VERSION"><![CDATA[00]]></string>
			<string id="SCRIPT_DESCRIPTION"><![CDATA[Utviklet av Rick USA]]></string>
			<string id="SCRIPT_HELP"><![CDATA[Funksjoner: 
1) advarer mot forsøk på å åpne doble forekomster av samme Notepad fil.
Utvikling Miljø:
Windows XP Professional med servicepack 3.
NotePad versjon 5.1.]]></string>
			<string id="GWToolkit_Required"><![CDATA[Dette programmet krever GW Toolkit.]]></string>
			<string id="DuplicateOpenFileWarning"><![CDATA[fil er åpen mer enn én gang.]]></string>
		</strings>
	</language>
EndCopiedCode:
The above block is the xml Language Element for the Norwegian Language.
*Step02:
Open WindowEyes and click Explorer The User Profile Folder under the File Menu.
In the Default Folder, 
Navigate to NotePad2011.xml and right mouse click the Edit item.
Paste the Norwegian Language Element xml we saved to the ClipBoard between the, 
Closing xml tag for the English Language Element  and the 
closing xml tag for the wescriptui tag.
Example:
	</language>
(Paste your Norwegian Language Element here)
</wescriptui>
Close the NotePad2011.xml file and save your work.
</053 Translate To Norwegian>

===<054 Test The Norwegian Language Element>===

We are now ready to test the new Language Element.
However, since we do not live in a country where Norwegian is the primary language WindowEyes will not know to use our new element.
Therefore we will modify another element in our NotePad2011.xml file to tell WindowEyes to use Norwegian as the current language.
To do this:
We will comment out the <languageorder>WE,OS,en-us</languageorder> Element.
This is because when NotePad2011.vbs is loaded, 
WindowEyes checks the <languageorder>
element to determine which Language element to use. 
Above the order would be:
first check the value in the first placeholder - WE
If it is not set then check the value in the OS PlaceHolder and
finally, if neither is valid, use a hard coded default value (en-us) in this case. 
Note that this is the Microsoft Language Code string for United States English.
*Step01:
Open WindowEyes and click Explorer The Profile Folder item under the File Menu.
In the Default Folder navigate and open the NotePad2011.xml file in the text editor.
(right mouse click it and select Edit).
*Step02:
Comment out the current <option>
We do this by wrapping the xml element in <!-- and --> xml comment elements.
It should look like:
BeginCopiedCode:
<!--
		<languageorder>WE,OS,en-us</languageorder>
 -->
*Step03:
Now add the following element above the comment block in the <options> element so your code looks like:
 BeginCopiedCode:
<code>
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <wescriptui>
 	<options>
		<languageorder>no</languageorder>
 <!--
		<languageorder>WE,OS,en-us</languageorder>
 -->
	</options>
</code>
 EndCopiedCode:
Note that above we removed the checks for Windoweyes to pull the LanguageCode from the WE or OS variables and changed the default language to "no".
This is the Microsoft LanguageCode for Norwegian.
Close the Editor and save your work.
*Step02:
Fire up Notepad and try and open the same file more than once.
This time you should hear your warning message in Norwegian!
*Step03:
Switch to WindowEyes while NotePad is still running.
in the App Manager  click Help for the NotePad.vbs Application.
The values we entered in the Norwegian Language element are used instead of English!
You are done with this Application for now.
Don't forget to remove or comment out the  test xml languageorder element:
"<languageorder>no</languageorder>"
When commented out it looks like:
BeginCopiedCode:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wescriptui>
	<options>
<!--
		<languageorder>no</languageorder>
-->
		<languageorder>WE,OS,en-us</languageorder>
	</options>
...
EndCopiedCode:

 </054 Test The Norwegian Language Element>

==<060 Creating The Installation Package>==

First we need to Create an Installation Package (a .wepm file).
Then we can Upload it to App Central.
Here we will WalkThrough the WindowEyes Package Manager Dialog.  The package manager is documented in the Window-Eyes App Developer's Reference Manual, the chapter named "An Introduction to Window-Eyes Apps", the section: "Packing Your App".

*Step01:
In WindowEyes under the Apps Menu expand App Management and click the Package Manager item.
The Package Manager Dialog comes up.
Tab to and click the  Create New Package Button.
A new Window Opens with the options we need to set.
*Step02:
Set or leave the Localized Language as "English".

Tab and enter NotePad2011 in the Name EditBox.

Tab and enter 0.3 in the Version EditBox.
(note: you need to specify the version number of your app in 3 separate locations: in the XML file, this field in the package manager, and a field in the app central dialog when you upload the app.  It's important that this version number be exactly the same in all 3 of these locations, and if you update your app, you must update all 3 locations.)

Tab past the empty "Files To Install" ListView.
In theFileInformation EditBox enter:
This app will notify you if you have more than one instance of a NotePad file open when you attempt to open another instance of the same file.
It uses no hot keys.

Tab and in the License EditBox enter:
No warranty of any kind exists. 
I understand I use this script entirely at my own risk.

Tab to theDefaultLanguage 		  ComboBox and slect English.

Tab and click the Add Files button.
In the Default Folder's list of files select NotePad2011.vbs and NotePad2011.xml then tab and click open.
You are returned to the package manager Dialog.
Ensure the 2 files are now in the "Files To Install" ListView.  

Now it is important to highlight the .vbs file, and then indicate to the package manager whether it is a global app, or associated with a program.  You do this by leaving the .vbs file highlighted, and tabbing to either the "associate globally" or "associate with a program" command buttons, and pressing spacebar on the appropriate button.  If you have selected the "associate with a program" button, then you will be asked for the name of the .we file which is loaded when the associated program is executed.  You can select more than one .we file, since an app can be associated with more than one program.  When you are done selecting the .we files and have clicked "ok", you will be returned to the package manager dialog, and the associated .we files will now appear in their own listbox similar to the listbox used for the list of files to be included in the package.  If you instead choose "global" as the association type for the main .vbs file, then you should see an entry in this "associate with" listbox which says "global".  It's important to note that you must choose one or the other type of association, so something should always appear in the "associate with" listbox when the primary .vbs file is selected in the "files to install" listbox.

Note: If you are modifying an existing wepm file and you see that your files are already listed in the FilesToInclude list you still need to Add the newer versions or you will get the old versions uploaded.  This usually means you will need to add both the .vbs file and the associated .xml file for each update.

*Step03:
Tab back to the LocalizedLanguage ComboBox and select Norwegian.
Tab and enter NotePad2011 in the Name EditBox.
Tab to and In theFileInformation EditBox enter:
Associated skript kan kjøres samtidig. 
Du trenger ikke å lesse av eksisterende tilknyttet scripts.
Tab and in the License EditBox enter:
Ingen garanti av noe slag eksisterer. 
Jeg forstår jeg bruke dette skriptet helt på min egen risiko.

* Step04:
Tab and click the Create Button.
A common Save dialog comes up.
Leave the name of the Installation Package as NotePad2011 tab and click Save.
You get a message the Package was saved.

* Tab to and hit the close button.

===To verify your package was created===

click the ExploreProfileFolder item under the File Menu.
Navigate down to the Notepad2011 entries and you should see:
NotePad2011.vbs
NotePad2011.wepm
NotePad2011.xml.
Close everything up - we are done!

 </060 Creating The Installation Package>

==<070 Add NotePad2001 To AppCentral>==

We will now add our NotePad2011 Ap to App Central so others can download and install it.

*Step01:
If you have not created your App Central Account WalkThrough Appendix A and create one.
An account is required to create and manage Apps on the WindowEyes App Central.
Once created, walkthrough the  following steps to add NotePad2011 to App Central. 
When complete others will be able to download and install it:
*Step01:
Navigate to App Central and Log in by entering your UserName and Password.
Navigate down to the link labeled "My Apps" and click it.
The Apps Management page comes up.
Anote:
You will hear the fields to enter data into followed by a help link inside what sounds like a EditBox.
The real boxes you want to enter data into or select data from will be after this "Boxed Link". 
*Step02:
Navigate to the "Add a New App" link and click it.
Navigate to the Name EditBox and enter: NotePad2011
Tab and enter 0.3 for the version number and hit tab.
A message comes up telling you you have changed the version and
that the Change history log will be cleared.
tab and click ok.
Tab and select Program Enhancements for the Category.
Tab Select 7.0 for the Minimum WindowEyes Version.
Tab and check English and Norwegian for the Supported languages.
Tab and select "English" for the Description Language:
Tab to the ShortDescription and enter:
Notify user if more than one instance of a NotePad file is being opened.
Tab to the LongDescription and Enter:
Speak a warning if a user opens more than one version of a NotePad File. 
Having multiple versions of the same file open can result in lost data if the wrong version is saved.

Tab back to the Description Language and select Norwegian this time:
Tab to the ShortDescription and enter:
Informer brukeren hvis mer enn én forekomst av en notepad fil blir åpnet.
Tab to the LongDescription and Enter:
Snakk en advarsel hvis en bruker åpner mer enn én versjon av en notisblokk fil. 
Å ha flere versjoner av samme fil åpen kan resultere i tapte data dersom feil versjon er lagret.

Tab and Leave the CheckBox labeled "leave Send automatic email announcement of app update." checked.
Tab to the Update Browse button and click it.
Click on the NotePad2011.wepm in the WindowEyes Default folder or, 
If you added it to another folder navigate to your NotePad2011.wepm file and click it.
Tab and click the open button to select and return to the installer main window view.
Note: 
You might have to get back into Browse Mode if WindowEyes does not return into BrowseMode.
You will see the path as c:FakePath.NotePad2011.wepm in the UploadFile ReadOnly EditBox.
I think this is a security measure during file transmission to the server. 
You may be able to route the mouse to this field and you will hear your actual path reading with the mouse.

Finally: Tab and click the Update App Button.
If all went well your Application is added to App Central.
</070 Add NotePad2001 To AppCentral>
<071 Testing The Installation>
Now that you have uploaded your app you will want to test the installation to ensure everything was uploaded correctly.
We want to make a clean environment prior to the download and install to mimic the state of another users environment.
To do this we need to 
Step01:
Open Notepad and hit control-\ to get into windoweyes.
In AppManager Unload the current NotePad2011 App.
Close AppManager:
Backup the NotePad2011.vbs, xml and wepm files then remove the package using AddRemove Packages under the App Management menu under the Apps menu.
Step02:
If you have Jamal's Installation App you can hit control-windows-i to open his installer.
Then follow the instructions to install NotePad2011 from App Central.
After the installation you should:
Open NotePad, go into AppManager and see the NotePad2011 App running.
Note: Make sure the Programs radio button is selected and not the Global or other radio buttons. 
or you won't see the NotePad2011 App in the list of running Apps.
Now, close AppManager and try and open a second instance of the same NotePad file.
In a couple of seconds you should hear the warning that you have more than one instance of the file open.
If this happens you are done.
You will see that the files we Backed up are ReInstalled in the Default Folder.
That's all for now.
Happy Programming!
Rick USA
 </071 Testing The Installation>

==<Appendix A: Set Up A App Central Account>==


You might want an account with App Central.
You need an account to put your script up on App Central and to 
register an e-mail account if you want to use the Extended Help feature in the WEFrameworkScript Wizard.
This means that when a user has a problem your script will automatically gather some details and e-mail you a notice of the error.
If you do not set up an account, 
you will be instructed not to check this option in the WEScriptFramework Walkthrough.

Step01:
Navigate to App Central:
The Webpage comes up:
Navigate down to and click the link: 
sign up for a App Central account
A Second Webpage comes up:
Navigate Down to the Registration Information Area on the page:
Enter a UserName, Password and Select a Challange Question and enter a Answer.
Then enter your first name,  Last Name and your E-Mail Address.
If you have a website you cqan enter it next or skip this box.
You can enter a general location like Detroit Michigan in the location box.
You can next introduce yourself.
Finally, tab and Click the Sign Up Button.
A e-mail is sent to the e0-mail address you specified above for verification.
Open it and click the link to verify your Registration.
You should now have a App Central Account:
Step02:
You can now log into your new account and select 
the link labeled: My Profile
Navigate down to the Error Reporting Header.
You will read:
BeginCopiedText:
To take advantage of the
GW Toolkit
 Error Reporting feature, you must enter a valid email address below (or multiple
email addresses, separated by comma). If you use the error reporting feature with
an email address that is not designated below, no error reports will be emailed to
you automatically.
Error Reporting Email(s):
Update Error Reporting Email button
EndCopiedText:
Put the e-mail address you want in the EditBox and click the Update Button.
Note: I just used the same e-mail address I Registered with.
The next page will have the message:
"Your error reporting email information has been updated."
You now have an Account with a valid personal e-mail address and a e-mail address to have your script's Error Messages sent to.
 </Appendix A: Set Up A App Central Account>

==<Appendix B: Microsoft MSDN Language Codes>  ==

URL As Of Article: 
http://msdn.microsoft.com/en-us/library/ms533052(VS.85).aspx
.NET Framework 3.0
The following table lists all the possible language codes used to specify various system settings.

af
Afrikaans
sq
Albanian
ar-sa
Arabic (Saudi Arabia)
ar-iq
Arabic (Iraq)
ar-eg
Arabic (Egypt)
ar-ly
Arabic (Libya)
ar-dz
Arabic (Algeria)
ar-ma
Arabic (Morocco)
ar-tn
Arabic (Tunisia)
ar-om
Arabic (Oman)
ar-ye
Arabic (Yemen)
ar-sy
Arabic (Syria)
ar-jo
Arabic (Jordan)
ar-lb
Arabic (Lebanon)
ar-kw
Arabic (Kuwait)
ar-ae
Arabic (U.A.E.)
ar-bh
Arabic (Bahrain)
ar-qa
Arabic (Qatar)
eu
Basque
bg
Bulgarian
be
Belarusian
ca
Catalan
zh-tw
Chinese (Taiwan)
zh-cn
Chinese (PRC)
zh-hk
Chinese (Hong Kong SAR)
zh-sg
Chinese (Singapore)
hr
Croatian
cs
Czech
da
Danish
nl
Dutch (Standard)
nl-be
Dutch (Belgium)
en
English
en-us
English (United States)
en-gb
English (United Kingdom)
en-au
English (Australia)
en-ca
English (Canada)
en-nz
English (New Zealand)
en-ie
English (Ireland)
en-za
English (South Africa)
en-jm
English (Jamaica)
en
English (Caribbean)
en-bz
English (Belize)
en-tt
English (Trinidad)
et
Estonian
fo
Faeroese
fa
Farsi
fi
Finnish
fr
French (Standard)
fr-be
French (Belgium)
fr-ca
French (Canada)
fr-ch
French (Switzerland)
fr-lu
French (Luxembourg)
gd
Gaelic (Scotland)
ga
Irish
de
German (Standard)
de-ch
German (Switzerland)
de-at
German (Austria)
de-lu
German (Luxembourg)
de-li
German (Liechtenstein)
el
Greek
he
Hebrew
hi
Hindi
hu
Hungarian
is
Icelandic
id
Indonesian
it
Italian (Standard)
it-ch
Italian (Switzerland)
ja
Japanese
ko
Korean
ko
Korean (Johab)
lv
Latvian
lt
Lithuanian
mk
Macedonian (FYROM)
ms
Malaysian
mt
Maltese
no
Norwegian (Bokmal)
no
Norwegian (Nynorsk)
pl
Polish
pt-br
Portuguese (Brazil)
pt
Portuguese (Portugal)
rm
Rhaeto-Romanic
ro
Romanian
ro-mo
Romanian (Republic of Moldova)
ru
Russian
ru-mo
Russian (Republic of Moldova)
sz
Sami (Lappish)
sr
Serbian (Cyrillic)
sr
Serbian (Latin)
sk
Slovak
sl
Slovenian
sb
Sorbian
es
Spanish (Spain)
es-mx
Spanish (Mexico)
es-gt
Spanish (Guatemala)
es-cr
Spanish (Costa Rica)
es-pa
Spanish (Panama)
es-do
Spanish (Dominican Republic)
es-ve
Spanish (Venezuela)
es-co
Spanish (Colombia)
es-pe
Spanish (Peru)
es-ar
Spanish (Argentina)
es-ec
Spanish (Ecuador)
es-cl
Spanish (Chile)
es-uy
Spanish (Uruguay)
es-py
Spanish (Paraguay)
es-bo
Spanish (Bolivia)
es-sv
Spanish (El Salvador)
es-hn
Spanish (Honduras)
es-ni
Spanish (Nicaragua)
es-pr
Spanish (Puerto Rico)
sx
Sutu
sv
Swedish
sv-fi
Swedish (Finland)
th
Thai
ts
Tsonga
tn
Tswana
tr
Turkish
uk
Ukrainian
ur
Urdu
ve
Venda
vi
Vietnamese
xh
Xhosa
ji
Yiddish
zu
Zulu
 </Appendix B: Microsoft MSDN Language Codes>  
 </Content>
Return to Walk-through for Creating an App.
Retrieved from "http://www.gwmicro.com/mediawiki/index.php/Walk-through_for_Creating_an_App"
View source - GWWiki

Navigation

Search

Toolbox

Personal tools
