> I still miss the ability to "Reveal Codes" and see exactly where it had placed the non-printing codes to turn on/off bold, italics, to change margins, etc. [...]
I wish there was some kind of standard to tell CLI apps what features to expect from the system pager, so they can act accordingly …
Right now, apps can talk to the terminal to check for feature support, but all of that falls apart when the output is piped to a pager. (Do we support inline links? ANSI colors? Sixel support??)
Shameless plug, specifically regarding Sixel support: I needed a pager with better image support than just less -r and made https://github.com/roblillack/lessi
Wow, this project (and actually the whole thread here) is awesome. Love it! Our (iPad-based) kitchen timetable[1] is nothing compared to the work (and money) Joel sank into this.
If someone wants to go the easy route towards something like this: iPad (Air 1, I think) is connected to the charger 24/7 and runs in Kiosk mode. Application is just a React website hosted on Vercel, client credentials are stored in localStorage …
It’s not PIC and not really suitable for complex diagrams, yet, but you can use Vizzlo’s Chart Vizzard to create a subset of the supported chart types (let’s say a Gantt) and then continue editing it using the chart editor: https://vizzlo.com/ai
For complex scenarios (i.e. the user interacting with the UI while there are some long-running processes in the backround doing this, too), managing the state quickly gets unwiedly: You need to write callback code everywhere that carefully has to inspect the current status of all other activities and might then updates 10s of widgets accordingly.
With the reactive approach you are able to write a single rendering function that describes the interface for any given state and the framework takes care of the rest (when to call that function, what "input" to give it).
It's just way easier to wrap my head around this and after working with React it is hard to go back. Hence the experiment to see if something comparable could be done in Go.
No, it just means that the main goroutine should not be moved onto another OS thread to ensure that it is always the same OS thread which will run UI updates.
This is necessary for most UI libraries and in Spot's case implemented for both the FLTK and the Cocoa backend.
Not a full replacement for WordPerfect, but Pure has "Reveal Codes" (F9): https://github.com/roblillack/pure