sciteco - Scintilla-based Text Editor and COrrector

Age	Commit message (Collapse)	Author	Files	Lines
2012-11-21	GTK interface: show window only before going into event loop (so it is not ↵	Robin Haberkorn	1	-1/+0
	displayed for longer running munged macros)
2012-11-16	fixed clearing message line: do not display an empty message line (which can ↵	Robin Haberkorn	1	-0/+8
	mean an empty line sent to stdout)
2012-11-16	keep a buffer dirty flag and display infos about the current buffer in the ↵	Robin Haberkorn	1	-2/+47
	interfaces (including the dirty flag) * was a bit tricky because the Scintilla SAVEPOINTS cannot be (fully) used * when a file is loaded or saved, a Scintilla SAVEPOINT is set * SAVEPOINTLEFT notifications are used to set a buffer dirty * SAVEPOINTREACHED notifications are useless since Scintilla does not consider the saves themselves to be undoable * GTK interface displays infos in window title bar * NCURSES interface has also been updated and cleaned up a bit. Infos are displayed in a new info line. * NCURSES: fixed popup display after terminal resizing
2012-11-15	NCurses interface: support terminal resizing	Robin Haberkorn	1	-1/+5
	* currently, the message line is not remembered and reset on termresize * any open popup window will be drawn over by the other windows
2012-11-15	support stdio for curses interface	Robin Haberkorn	1	-20/+6
	* ./sciteco commandline help works now * messages issued during batch-mode macro processing are written to stdout/stderr * output can be redirected
2012-11-15	changed default colors and moved stuff into user interface	Robin Haberkorn	1	-0/+4
	* hardcoding the colors is only preliminary * focus must be set in interface
2012-11-15	cleaned up command line updating: the interface is responsible for drawing ↵	Robin Haberkorn	1	-3/+7
	the "*" (if it wants to)
2012-11-15	added Interface class to ease porting SciTECO to other platforms (toolkits)	Robin Haberkorn	1	-0/+196
	* will support Scintilla with Scinterm/NCurses * changes are in such a way that the generated machine code should have almost no overhead compared to the previous implementation (at least when compiled with optimizations)