xpath8 wrote:Why don't you have a GUI-based editor for your script language?
The simple answer is that none is needed. Here's why...
Users familiar with eValid understand the benefit of having the simplest possible script language -- really, it is closer to being a "command language" because it is so simple. Simplicity was a design point at the beginning of the development of eValid and it has stayed true to that principle.
eValid commands are one per line, blank/white-space delimited, and of any length. (There is a line continuation method if you need it but most of the time you don't.)
The only thing that can get complicated in an eValid command is when you have a character string which includes blanks, and it that case you will need to enclose it in "'s, for example
"like this".
So, our thinking goes, which add a complicated GUI-based command line editor when the commands are so simple? What add complexity when it is not needed? And, why force editing to be done in ONE way, when, as eValid is now, you can edit the scripts that drive the eValid browser with any editor you want.
Better you should use your own editor, with which you're familiar, than having to learn [yet another, non-standard] editor.
The eValid Support Team
by xpath8 » Mon Jan 17, 2011 5:24 pm