Replies: 1 comment 1 reply
-
|
Years ago I ported an entire ncurses library to ELKS. It is in the source tree under elkscmd/nano/ncurses-5.2, go ahead and look at it, if you dare. The "standard" ncurses library is so big, so huge, so ugly inernally, so incredibly difficult to configure, and so incredibly large once compiled that when linked with "nano", the supposedly-super-small Linux/UNIX WYSIWYG screen editor, that the combined memory usage of the two of them linked togeher produced an executable that literally had enough application data space left to edit files that contained no more than a single line of text, else they would run out of memory. Thus, I definitely do not recommend getting anywhere near close to even thinking about using ncurses for programs on ELKS. Also, the ELKS console is ANSI-only, with no need for termcap, making another large part of any curses-like library unnecessary, unless trying to port some monster UNIX program that is supposed to work on all Unices. I did write a very small extremely basic curses replacement in elkscmd/tui (curses*.c) for ease of porting very basic or otherwise tiny ncurses-based applications. It doesn't support any window memory, and one kind of has to know what the applciation needs in order to use it, but it's there, and is used for programs like
What programs specifically are you looking for? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Anyone brave enough to try a port of some sort of Curses library to elks?
I am in dire need for a bunch of network cli apps i want to port over to elks to play with.
Beta Was this translation helpful? Give feedback.
All reactions