>>Well, you can do that right now, correct? Just save as a VCX and go turn it into code in the OB. <<

The OB doesn't produce "executable" code, unless the object hierarchy is trivial. In any event, it's only "one-way".

I was refering to "two-way Programming"; ie. what Delphi, Kylix, Visual dBase and to only a lessor extent, VB and VC++ all support. All these platform save as ASCII and as long as you don't go nuts, you can modify the ASCII files and the "IDE" accepts your changes. They don't have problems with "hierarchies" either.

But then again, I'm probably the only that thinks I'm more productive working with text vs bumbling thru umpteen IDE windows when I'm not just "painting".

>> Unless someone could come up with a way to create non-visual classes via some sort of definition mechanism/screen...<<

I don't know what this means; I only implement "non-visual" classes in (PRG) code to start with ... and my text editor works just fine in those cases. Creating a "non-visual" VCX class is pointless, IMO; particularly when it means giving up (simple) global text searching, replacing, browsing, etc.