Thus I baptized the kind of the programming, in which one can arrange programs clearer by own inserting of style information (like e.g. bold print, colors, etc.). The used principle of this editor in addition, is actually completely simple: To each file there is the possibility to store by the so-called "twin mode" additionally to the text file also a rtf file simultaneously and automatically. The file name of this auxiliary file is simply the file name of the text file extended over" .rtf ". While the loading of the text file it is recognized automatically whether there is an associated rtf file. There is such a file is compared whether equal to files it is (momentarily over read Modified), and if, then the rtf file loaded instead of the text file. Thus it is possible to store in a text file also style information. Because the style information is in the rtf file there is no problem to e.g. compile Java programs.
By this "new" kind of programming one can use style information e.g. for the following:
- emphasize new code lines through e.g. green
- emphasize became outdated code lines, which one has soon forwards to removing through e.g. light blue
- mark important function calls by larger writing
- emphasize !determined! comment lines by red color , and others leave in such a way
- mark places in which one later in any case still want to insert code (e.g. safety inquiries not programmed yet), e.g. by very large red writing.
- marks implemented lazy algorithms which one wants to revise because of performance-purposes.
- and much more besides, no borders are set to own creativity when marking.
Advantages are (beside the above) that…
- … one !one! editor for programming and possible documentations to the program have. One does not need to open 2 editors to have thus with a documentation or a to-do list.
- … because PIEdit is programmed in Java, one can use on all platforms (it is Windows, Unix, or other one) the same editor
- … because PIEdit does contain special functions for DOS and Unix files clean-loads of the different file types are no problem. Like that it is e.g. with the Xemacs editor of Unix the case, which produces when the DOS files loaded at each line end ^M, there these the CR (0d) of the DOS files represents.
- … under Windows also certain INI files (like e.g. with the Haupauge WinTV card remote maintenance file "irremote.ini") can decorated with styles for clarity of the content.
The disadvantages are that…
- … one when intermediate use another editor than PIEdit the entire style information inevitably loses (files no longer identically)
- … Syntax error to be more heavily recognized
