I hope you're not talking about <iframes>. Each "control" already has it's own invisible "handle", and that handle provides common functionality to the control using prototyped members.
Ok, I'll just give another example of where I would be able to use the answers to the question I'm asking...
The OS is divided into three sections, Applications, Controls and Objects. Each are allowed to specify dependencies. So an Application can ask for the Window control to be loaded prior to being executed. Same thing goes for the Window Control requesting the Menu system to be available.
So currently to build a Menu you would write:
var Menu = CreateObject('os.menu');
And to show it, after defining some items, you would write:
The Menu provides some constants you can use to change how it's displayed, but they are part of the Menu object you just created.
Menu.Show(element, Menu.VERTICAL | Menu.BOTTOMALIGN);
But I wanted to know if writing those values into an outer scope was possible so I could just write...
Menu.Show(element, VERTICAL | BOTTOMALIGN);
Using the "with" keyword it has been completely possible... but I'm wondering if I should sacrifice using strict mode just to use it.
If it doesn't click now I think I should give up