Well tbh, I am trying to shy away from having to create or include extra namespaces at all. I want to make Kixforms more like the Office or Internet Explorer COM objects, were one just simply "includes" a global namespace reference like:

code:
$Excel = CreateObject("Excel.Application")
 
$IE = CreateObject("InternetExplorer.Application")
and then ALL the objects are derived out-of the single namespace. I find this approach (imho) much more intuitive then the DOTNET approach of having a bazillion includable namespaces. I guess the problem is, I am try marry the single namespace approach with the multiple one used by dotnet.

But getting back to your idea, assume there was an object with a namespace path like this:

code:
Kixtart.Drawing.Font
and then one did this:

code:
$Forms.Include("Kixtart.Drawing")
Would the object be then referenced directly out of the root, like this (because it was "included"):

$Forms.Font

or would include the namespace into the root just extend the root with a new property called Drawing, and the object would still be referencd like this:

$Form.Drawing.Font