vdsalchemist Admin Team

Joined: 23 Oct 2001 Posts: 1448 Location: Florida, USA
|
Posted: Mon May 14, 2007 3:34 pm Post subject: |
|
|
Here are some facts about GadgetX syntax...
VDS is the reason most of the GadgetX syntax is the way it is. VDS DLL's have very specific rules that they have to follow. Also VDS DLL's have to follow all the rules of Windows DLL's as well.
Starting with VDS 5.x VDS DLL extentions are allowed to define more than one Command/Function name. GadgetX takes advantage of that.
The GadgetX syntax leans towards BASIC and C since these are the languages I am most familiar with.
Most of the GadgetX commands and functions have both a long name and a short name. The reason for the long name's and short name's is that if some other DLL, DSU, or user defined command/function has the same name you will be able to still use GadgetX without the need to have the other components change their names. So you will see some of my demo code using the short name while others use the long name. Here is an example of defining variables with both the short names and long names.
| Code: |
External GadgetX.dll,5.0
#DEFINE COMMAND,DEFINE,DEF,SET,SETVAR
#DEFINE FUNCTION,GET,GETVAR
# This line uses the long command names
Define Variable,DWORD,MyDword
# This line uses the short command names
Def Var,INTEGER,MyInt
# These lines use the short names
Set MyDword,25
Info @Get(MyDword)
# These lines use the long names
SetVar MyInt,-25
Info @GetVar(MyInt)
|
GadgetX does not try to discover anything on it's own. The DLL needs almost everything defined upfront before you use it. The reason for this is due to speed. It takes more time for a program to try to figure out what you want than it does for you to tell it what you want. The Define command is the key command to making everything in GadgetX work.
Ok I can go on but I think I will start a tutorial type thread in the "Other Product Support/Announcements" forum...
I will try to keep it simple and slowly build onto it. _________________ Home of
Give VDS a new purpose!
 |
|