Simple text-editor to write text-files and add, insert and edit lines.
Grubutil FAT is mandatory, and is used for saving (saving only on FAT-devices!).
FATTEXT.G4B is not a conventional editor, but operates with individual lines.
More or less the same as the grub4dos menu-editor, but with more functionality. However the grub4dos menu-editor has access to the full command-line (in a separate 'window').
FATTEXT.G4B uses the 'set /p' command-line, so max 510 chars, and no starting space just like the regular command-line in grub4dos. In most modes there is 'cheating': starting char 'underscore' is converted to a starting space. Longer lines can be made by (backwards) joining lines.
Editing long lines is done by splitting in smaller parts. So not convenient, but most of the time not a 'real' issue.
The convenient part of the 'set /p' command-line is direct access to the grub4dos History Buffer. Especially because cut/ copied/ edited lines are copied to the History Buffer first (based on sub-routines I developed for KEYBUFF.G4B - now HISTBUFF.G4B).
Some action print-screens.
First print-screen shows a file after opening from command-line, directly in Edit-mode, with menu-items. On last line there are messages and length of the 'active' line:
Second print-screen shows next 'page', after PageDown (or using 'T'). Length of 'active' line is highlighted, will be split if edited:
BTW: pages are continually calculated. Going down is 'best', going up is not always fully the same if the page was filled up with first part(s) of a line.
Third print-screen shows help for Edit Menu after pressing F1. As can be seen more to the bottom, there are some hidden menu-items like Ctrl+O, Ctrl+S, Ctrl+B and my favorite: Alt+F4:
Fourth print-screen shows editing of a line, if longer than 74 chars the wrapped parts can be still seen during editing (see Line 13):
BTW: the 'set /p' command-line is not so fast however, 'walking' with ArrowRight or ArrowLeft. Further Home or End only.
Fifth print-screen shows the result of the search-function (at the limit of max 80 chars), with replace-command-line already activated, ready to replace:
BTW: on the bottom a greyed-out message can be seen with more details about the Replace function
Sixth print-screen shows the Main Menu, some functions like New (text-file), (Save)As, Convert and Graphics can only be accessed from in this menu:
BTW: last active line is still visible, but has normal text-color.
Seventh print-screen shows the Convert Menu:
BTW: inside FATTEXT.G4B always MS-DOS text-mode is used, Unix/ (old) Mac text-modes are auto-converted during opening and saving. So convert to another mode is an extra function to change the text-mode type of an existing file.
Eighth print-screen shows the Graphics Menu, item Color (28 presets), ninth and tenth print-screen's are showing two results after changing Color. On tenth print-screen History of the Open Menu is showed, choosing by number 0-9 is possible, a bit like MS-DOS editor 'Edit':
BTW: all configurations are saved to the file FATTEXT.DAT, Color too.
Eleventh print-screen shows a new function I have not seen in the text-editors I normally use: Backup file to a different name, without changing the name inside the editor. Menu-item File is already activated, original file-name is 'raised' from the History Buffer ready for editing:
Last print-screen shows the folder/ file Browser:
BTW: the Browser is a bit primitive, only viewing folders/ files, choosing by manually inserting number-of-choice. In Save-mode new folders can be made on a FAT-device by inserting them in item Path, one menu-level up (full path must be used or inserted, new folders are immediately created - max 18 levels 'deep').
More information is in the Readme on GitHub.
I started this project about two years ago, most complicated project I ever worked on.
I'de like to thank Wonko the Sane and steve6375 for help and advice.
More details about the project can be found in my thread 'Writing to the Grub4dos' keyboard buffer possible?',
starting here: http://reboot.pro/in...=22450&p=218439
