Universal Document (.udoc) is a software concept I originally programmed for use in my Code Toolbox G@ software development platform. It actually is quite simple in construction in that it is actually two documents in one. It is a full function bitmap used as a background and has a full word processor that overlays text in any way over the bitmap background. The two are combined into one file in which a suitable compression scheme is employed for file storage. Magazine quality documents can easily be made with it.
The original purpose of it was the capability to program things such as dialog boxes and have all the image bitmaps right with the code all in the same document. This makes importing and exporting code to different projects a snap being a simple thing to move one single udoc file around instead of the more cumbersome methods typical in programming systems today. How it all got started is from my @on microprocessor concept and how it has a unique instruction set requiring that I write all the programming software for it.
It also uses what I call a black character concept which is useful in program editing. A typical udoc screen background that is blank is usually gray so that editing characters such as return and tab show up as black characters making them easy to see, or avoid, for select, cut and drag operations. Also other colors show up best on a gray background it being the best for enhancing any other color. Foreground characters are normally yellow or green which are colors chosen because of their minimal effects on eyestrain as compared to the tortuous effect on the eyes that a glaring white background and antiquated raster scan video technology can cause.
It contains all of the usual drawing tools and any3bytepicture.bmp can be imported. Furthermore I continue to add tools to facilitate and expedite the production of drawings for inclusion into the vCAD engineering software currently under development. Many such engineering jobs require a unique set of drawing tools tailored to specific requirements and this is met most suitably with the O3S dockable software/tool system.
I'm currently enhancing my Code Toolbox code and my .udoc code so that they will work with my new .box file concept along with enhancements to bring it up to date and compliant with O3S file format requirements along with sundry software reconfiguration and efficiency improvements. Box is an archive type file that I decided would be very useful for combining project files and code libraries and any other groups of like subject data into a single file which has advantages for certain uses. It is easier to keep track of one file instead of dozens of files scattered all over the place. The .box file will be implemented directly into the O3S Media Peruser function. The O3S box archive file system is very flexible and I even intend to use it to store O3S compatible vax multimedia files.
O3S means Object Oriented Operating System and it is being developed by Mescitadel Think Tank and it will become the standard of operating systems like no other. Simple. Reliable. Effective. More than any other out there and believe you me, this I know from experience. O3S treats file and intra-net security very seriously and will eventually make a big difference.