Curses - Revision history

Agember at 20:18, 23 May 2008

2008-05-23T20:18:05Z

Agember at 23:09, 3 January 2008

2008-01-03T23:09:26Z

Agember: Started page

2007-09-13T23:16:55Z

Started page

Agember: Grammar fix

2007-08-28T22:10:47Z

Grammar fix

Agember: Note on current implementation

2007-08-28T22:10:29Z

Note on current implementation

New page

A Curses library, following the ncurses API is currently being implemented.

← Older revision		Revision as of 20:18, 23 May 2008
Line 1:		Line 1:
		+	{{Historical}}
		+
	[http://en.wikipedia.org/wiki/Ncurses Ncurses] is a programming library API for implementing text user interfaces. Currently, XINU's interface for output is limited to sequential lines of output using the [[TTY_Driver \| TTY driver]] and [[UART_Driver \| serial driver]]. The addition of an ncurses library in XINU would allow for more advanced text based interfaces.		[http://en.wikipedia.org/wiki/Ncurses Ncurses] is a programming library API for implementing text user interfaces. Currently, XINU's interface for output is limited to sequential lines of output using the [[TTY_Driver \| TTY driver]] and [[UART_Driver \| serial driver]]. The addition of an ncurses library in XINU would allow for more advanced text based interfaces.

@@ Line 4: / Line 4: @@
 Ncurses is designed to be a terminal independent API for text based interfaces.  This terminal independence requires a multi-layered internal implementation of the ncurses library.  Adding the actual ncurses implementation into XINU would double the size of XINU boot image.  Also, the standard ncurses implementation is highly complex, a contrast to XINU's clean code base.  XINU only has one terminal so the additional complexity of terminal independence is unnecessary for XINU.  Therefore, attempts are being made to implement a clean ncurses library for XINU.
-Starting from the original [http://en.wikipedia.org/wiki/Curses_(programming_library) curses] library is fairly straight forward.  However, original curses does not provide color, text formatting, or other "cool" features that would make a text based interface for XINU worthwhile.  Instead, the ncurses API, which includes these additional features, must be implemented for XINU.  The ncurses API is much more complex.  For example, multiple functions add characters to the screen: <code>addch</code>, <code>waddch</code>, and <code>mvaddch</code>, <code>mvwaddch</code>.  The main function is <code>waddch</code>, while the other three are macroed to move the cursor or specifing a specific window to which the character should be added.  All this adds up to a snarly mess that can cause the implementor to curse when the ncurses implementation just won't work.
+Starting from the original [http://en.wikipedia.org/wiki/Curses_(programming_library) curses] library is fairly straight forward.  However, original curses does not provide color, text formatting, or other "cool" features that would make a text based interface for XINU worthwhile.  Instead, the ncurses API, which includes these additional features, must be implemented for XINU.  The ncurses API is much more complex.  For example, multiple functions add characters to the screen: <code>addch</code>, <code>waddch</code>, and <code>mvaddch</code>, <code>mvwaddch</code>.  The main function is <code>waddch</code>, while the other three are macroed to move the cursor or specifing a specific window to which the character should be added.
 == Resources ==

← Older revision		Revision as of 23:16, 13 September 2007
Line 1:		Line 1:
−	~~A Curses~~ library, ~~following~~ the ncurses API, is ~~currently~~ being implemented.	+	[http://en.wikipedia.org/wiki/Ncurses Ncurses] is a programming library API for implementing text user interfaces. Currently, XINU's interface for output is limited to sequential lines of output using the [[TTY_Driver \| TTY driver]] and [[UART_Driver \| serial driver]]. The addition of an ncurses library in XINU would allow for more advanced text based interfaces.
		+
		+	== Why it is called curses ==
		+	Ncurses is designed to be a terminal independent API for text based interfaces. This terminal independence requires a multi-layered internal implementation of the ncurses library. Adding the actual ncurses implementation into XINU would double the size of XINU boot image. Also, the standard ncurses implementation is highly complex, a contrast to XINU's clean code base. XINU only has one terminal so the additional complexity of terminal independence is unnecessary for XINU. Therefore, attempts are being made to implement a clean ncurses library for XINU.
		+
		+	Starting from the original [http://en.wikipedia.org/wiki/Curses_(programming_library) curses] library is fairly straight forward. However, original curses does not provide color, text formatting, or other "cool" features that would make a text based interface for XINU worthwhile. Instead, the ncurses API, which includes these additional features, must be implemented for XINU. The ncurses API is much more complex. For example, multiple functions add characters to the screen: <code>addch</code>, <code>waddch</code>, and <code>mvaddch</code>, <code>mvwaddch</code>. The main function is <code>waddch</code>, while the other three are macroed to move the cursor or specifing a specific window to which the character should be added. All this adds up to a snarly mess that can cause the implementor to curse when the ncurses implementation just won't work.
		+
		+	== Resources ==
		+	* Strang, John. ''Programming with curses''. Sebastopol, CA: O'Reilly, 1986.
		+	* Gookin, Dan. ''Programmer's Guide to nCurses''. Indianapolis: Wiley, 2007.
		+	* [http://www.gnu.org/software/ncurses/ Announcing ncurses 5.6]

← Older revision		Revision as of 22:10, 28 August 2007
Line 1:		Line 1:
−	A Curses library, following the ncurses API is currently being implemented.	+	A Curses library, following the ncurses API, is currently being implemented.