I'll get the ball rolling on this one...

1) User-defined functions with declared parameters and return values...

if myfunc ( $x, $y ) > 100
...

:myfunc ( $x, $y )
return $x + $y

This is my biggie !

Of course - the parameters $x and $y of MyFunc() will have local scope, be stackable and support recursion.

2) Regular Expressions

C[AOU]T - Would match : CAT, COT, CUT only
C.T - Would match : CAT, CaT, C1T, C:T NOT CT
CA?T - Would match : CT, CAT only
C+T - Would match : CT, CCT, CCCCT
C(HE)?A[TP] - Would match : CHEAT, CAT, CHEAP, CAP only

This is my second biggie !

3) Auto Increment/Decrement operators ++, --

The statement $count = $count + 1 ...becomes... $count++

4) Assignment operators +=, -=, *=, /=, %=, >>=, <<=, &=, ^=, |=

The statement $total = $total + $subtotal ...becomes... $total += $subtotal

5) For loops...

For $counter = $start To $end [Step $step]
[statements]
[Exit For]
[statements]
Next

6) Formatted output strings for text and numerics...

?"Your balance = " format($balance*100,"$999,999.99")

We can only hope that Ruud listens. I agree though, KiX is dynamite. It's robust, intuitive and easy to learn !

Shawn.

[This message has been edited by Shawn (edited 01 May 2000).]

7) The full suite of UNC and Filename parsing functions ...

$path = "\\SERVERNAME\SHARENAME\DIRECTORY\FILENAME"
$servername = GetUncServername ( $path )
$filename = GetUncFilename ( $path )
$extention = GetFileExtention ( $filename )

8) Floating point arithmetic ? Anybody have any comments on this one ???

9) "BREAK" and "CONTINUE" type statements for do/while loops ...

10) An "ON BREAK GOTO HANDLEIT" type statement that will trap users hitting ^c (or killing the task) so one can clean-up any doo-doo. Don't know how this would effect the built-in logoff feature of "BREAK OFF" ???

Come on - I'm sure we can think of some more !

Shawn.

[This message has been edited by Shawn (edited 02 May 2000).]

Jos

the kix32 processor window running as a 'windowed app' instead of as a 'dos window'

the ability to log the screen output to a text file at the same time without using 2 display commands

additional features that operate like SetWallpaper, such as: SetScreenSize and SetScreenSaver

functions to return: amount of ram, specific OS build (better than @inwin and @dos), service pack level, and hardware devices like sound, NIC, and video make/model

Personally, I like kix32 just fine and I can make it do almost anything necessary. Like most things, the more stuff that gets added to it the more complex and unreliable it may become... anyone know the line count of windows 2000 :-)

$array[n] = shell "dir /b"

13) add a switch to disable logging to KIXTART.LOG in the TEMP directory

1. Feature of built-in encryption, irreversible encryption, rather than plain text format, to disable user to read Kix script easily. Forget about all those functions which try to encrypt Kixtart script, I admit they are all good, only with some exceptions that it will take longer to run the script on the client side.

2. Present in GUI, please..., with progress bar showing the completion of script execution. DOS windows box UI can be used only for debugging script.

Cheers,

2, OLE functions update => anything goes

anyhow thx Ruud for a fantacstic program

My suggestion for Rudd is "Next time sell the program - Get Rich"

Time to get this condensed down to a list... maybe in a new thread

1) Text should scroll inside the box.

2) You should be able to open more than one box, then set focus and write to each box separately.

3) Ability to open a box, close the box and have screen behind box restored to previous condition.

Thanks,
Mark P.

Boolean algebra: XOR

Inline Assembly: I don't expect it

Character level file manipulation: Instead of Line level

Variable value substitution: Instead of $a="blah", $b=chr($a), $c=$a AND $b, $d=asc($c), $e=val($c) I would like to just $b=val(asc($a AND chr($a))).

.EXE compiler or at least some way of putting the .KIX file into the KIX32.EXE file and creating USERDEFINED.EXE that cannot be dis-assembled.

Otherwise KIX is great, good work Ruud!

cj

In Turbo Pascal I can goto a point on the screen and get the char and screen attribute from that point and save it to a variable. I would like a similar function from kix.

This also means adding better colour support (yes, there is a U in colour) Instead of the r+/n I would like to use numbers in hex:
0-7 for the dark colours, 8-f for the light and blink.

so first nibble is foreground and second is background. 00 is black on black 10 is dark blue on black. 1F is blue on blinking grey etc...

The GETSCREENATTR function would return this byte (decimal is OK) for the current cursor position. SETSCREENATTR would set the color for the cursor position.

GETSCREENCHAR to get char at cursor.

Better Hex to Dec conversion too, not just oneway display.

that's it for now,

cj