This is not required, you are even free to use no prefixes at all, but these naming conventions do make debugging a lot easier.
gvsVar for strings, gvoVar for objects, gvaVar for arrays. In HTAs, however, I use those prefixes for local variables only, and use prefixes starting with gv for global variables, e.g. strVar for strings, objVar for objects, arrVar for arrays. I use 3 letter prefixes for all variables in my VBScript scripts, e.g.
HTAs aren't restricted to HTML and VBScript, you can use JScript and JavaScript without the need to install anything, and PerlScript if you install Perl. VBSEdit comes with a built-in debugger, but debugging an HTA is much harder then debugging VBScript code, so I usually write and test VBScript code in VBSEdit, and when ready, use it in an HTA's subroutines. It used to come with a separate program HTAEdit in a single package, but recently these programs have been merged, and the new VBSEdit now handles HTAs too. My preferred tool for developing HTAs is VBSEdit. On this page, I intend to show some of the pitfalls I encountered in building HTAs, and some solutions or work-arounds. If you need to build a proof of concept for a new program, consider an HTA. If you want to build a nice looking user interface for your VBScript scripts collection, try an HTA (or rewrite them in Visual Basic).
In fact, if run with elevated privileges, HTAs have access to every resource that administrators have access to! Though the engine that executes HTAs (MSHTA.EXE) shares a lot of code with Internet Explorer, it doesn't have Internet Explorer's tight security restrictions. HTAs ( HTML Applications) are webpages (forms), with access to local resources. Improve Loading Speed With MultiThreading.