🚀 go-pugleaf

EB> void turbo_qsort(...)
EB> 
EB> +-----+
EB> |Info |
EB> +-----+
EB> 
EB> An even better technique might to encode items with further documentation
EB> with a special color.  Selecting such specially colored items would make
EB> their comments visible, but by default the source code would not be
EB> cluttered
EB> with comments.

EB> Well the "gunk" is implicitly stripped.  You only get it if you ask for it
EB> by selecting the icon.
EB> 

Altough your idea is quite interesting, there is a technical problem:
ASCII files are the standard way to represent source code. They can be 
processed by nearly every machine, operating system, WAN and - most important - 
programming tool. But you can't include objects in ASCII files. So the compiler 
/ IDE will introduce a own representation. Even if the compiler vendors for 
Windows compilers will agree on a common standard, this will be limited to 
windows, because OLE is a sole windows feature. OK, the easy way is a Command 
"Save as ASCII", but than your graphical comments will be lost. Such a stripped 
version of your code will be even less undestandable as the old style ASCII 
commented version. I am afraid that a OLE IDE will be usefull for internal 
documention but not for distributing source over the net.