MobileRead Forums - View Single Post

knc1 · 05-18-2012, 10:50 AM

That may be a "speed bump" in the ncurses plan.

Although it is a character (rather than graphic) display, ncurses internals depend on only needing to refresh a minimum amount of the display (as in: direct character addressing).

Another entry for the: "to be researched" list.

Edit:
Perhaps just an ANSI sequence "overlay" for the e-ink display and touch screen input would do the job.
Anyone up to writing a VT100 ANSI sequence to e-ink display layer?
ncurses will run on __anything__ that understands VT100 ANSI character control sequences.

05-18-2012, 10:50 AM	#15
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	That may be a "speed bump" in the ncurses plan. Although it is a character (rather than graphic) display, ncurses internals depend on only needing to refresh a minimum amount of the display (as in: direct character addressing). Another entry for the: "to be researched" list. Edit: Perhaps just an ANSI sequence "overlay" for the e-ink display and touch screen input would do the job. Anyone up to writing a VT100 ANSI sequence to e-ink display layer? ncurses will run on __anything__ that understands VT100 ANSI character control sequences. Last edited by knc1; 05-18-2012 at 10:59 AM.