I'm back in the flow of learning the #Commodore 64 & #GEOS inside out, & reading code in geoWrite is such a pain. Text rendering is necessarily slow, but assembly is tall columns, the default margins/tabs cause frequent re-renderings, & the default font (BSW 9) is tall.
My first GEOS program is likely going to be a text editor. If I can't get geoWrite's format right, I can do pure ASCII & import it via Text Grabber with Generic II Form.
Cross-compiling would probably be better, but I don't want to. The quirks of that old great machine just make using it a joy, & emulators don't diminish it enough to matter.
Speaking of geoWrite...
Ever wanted to know how a featureful GUI word processor with only a single 0.001 GHz CPU, only 0.00006 GB of RAM, and only 0.000153 GB of storage space could pull that off?
Reverse-Engineered geoWrite 2.1 for C64 Source Code: https://www.pagetable.com/?p=1512
The article embeds a whole series of articles about how BSW pulled off a modern WYSIWYG word processor in such a tiny space.
There's geoText, but there's no manual, & I can't figure out how to type vital ASCII characters like the vertical bar (U+007C), geoAssembler's bitwise-or operator.
geoText:
- https://ftp.pokefinder.org/index.php?s=geoText&m=0&h=100
- http://www.zimmers.net/anonftp/pub/cbm/geos/productivity/index.html