roflmao, you sheephurter you. No, I am struggling with something on Kixforms right now. The damn Namespace issue is driving me insane. Its important and I want (have) to work it out now as opposed to later.

Its not a technical issue, its a usability/optics issue to do with the overall "layout" of how objects are instantiated in Kixforms vs dotnet.

In dotnet, there are dozens and dozens of different namespaces, some usefull and some totally useless (as far as Kixtart and scripting are concerned). For example, in dotnet, to create assign a Font object to a font property one specifies this:

Form.Font = System.Drawing.Font("Verdana",12)

and to start a process:

Proc = System.Diagnostics.Process.Start("Notepad.exe")

well, I have gone and implemented some of these namespaces (ie, Drawing) but I am finding that the code is getting very long-winded and overly complicated, for example:

$Form.Font = $Forms.Drawing.Font("Verdana",12,$Forms.Drawing.FontStyles.Normal)

What I have been playing with lately, is a simplified version of the namespaces, with every object (all of them) availble from the root namespace. This tends to make things easier to understand and (importantly) remember:

$Form.Font = $Forms.Font("Verdana",10,$Forms.FontStyles.Normal)

$Object = $Forms.Object()

$Process = $Forms.Process.Start("Notepad.exe")

$File = $Forms.File.Open("x.tmp")

so bascially, all the dotnet objects from the various namespaces (drawing, diagnostics, IO) would be made available throught the root namespace called $Forms (Kixtart.Forms)

Anyway, like I said, still doing much coding to determines which "style" I like better.