[ clisp-Feature Requests-1339718 ] screen & keyboard interaction

[SourceForge.net <no...@so...>]

Feature Requests item #1339718, was opened at 2005-10-27 13:11
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=351355&aid=1339718&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: UI
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
>Assigned to: Nobody/Anonymous (nobody)
>Summary: screen & keyboard interaction

Initial Comment:
add setfable accessors:
(SCREEN:TEXT-COLOR window-screen)
(SCREEN:BACKGROUND-COLOR window-screen)


----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2010-10-05 16:46

Message:
in general, clisp screen/keyboard interaction facilities are ancient and
probably not used too much (if at all) by the users.
this is obvious from the fact that (read-char *keyboard-input*) returns a
SYS::INPUT-CHARACTER whose accessors are not exported.
Proposal:
- move screen & keyboard streams from stream.d into a separate module
(window-stream and keyboard stream do not have to be lisp streams, and if
you think they have to, you can use gray streams) together with
xcharin.lisp.
- make keyboard input recognize _all_ keyboard events (e.g., now f1 is
recognized by ctrl-f1 is not).
- resurrect the ancient src/editor.lsp (?) in the same module(?); make it
more emacs-compatible.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2005-11-02 09:46

Message:
Logged In: YES 
user_id=5735

for unix you can use ncurses
http://www.google.com/search?q=ncurses
we already require them for readline.

tree of sreams is not really necessary:
just add x-offset/y-offset/width/height arguments 
to window-stream creation.

----------------------------------------------------------------------

Comment By: Arseny Slobodyuk (ampy)
Date: 2005-11-01 20:06

Message:
Logged In: YES 
user_id=553883

I thought about it 1000 times and since I don't know how to 
use colors on UNIX, didn't implemented. Tree of streams is 
too cool, on windows there is a system function to scroll 
console region and it even is used in current SCREEN code 
to scroll whole screen. Having lisp interface to it one can build 
his own nice libraries, using generic streams for the nice 
example given above. Again, threre is a question how to 
make this scroll function portable. And how to name colors 
portably, on windows there's Red, Green, Blue w/without 
intensity for text and same R, G, B w/without blinking for 
background. 


----------------------------------------------------------------------

Comment By: Don Cohen (donc)
Date: 2005-11-01 16:52

Message:
Logged In: YES 
user_id=8842

I have some code (actually quite old, but still in use) that
does the
scrolling subwindow part.  I haven't tried it with screen in
some time
so it might not quite work there.  I gave up on screen a
long time ago
and use ansi terminal emulation instead.  It turns out this
is not so 
easy to get these days in win-xp, but pscp does it, so one
way to use 
this stuff from win-xp is to ssh to a machine with an ssh
server.
(Anyone know where to get an ssh server for win-xp?)
Ansi terminal emulation is also a good way to control colors.
I can offer code for that too.
I've put the window code at
 http://don-eve.dyndns.org/windows.lsp


----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2005-10-27 13:32

Message:
Logged In: YES 
user_id=5735

another nice thing is being able to split the screen
so that scrolling in different parts is done independently.
I remember being able to do somehting like that 
with turbo pascal 5.5 15 years ago. :-)
(this would make it necessary to introduce a _tree_ of
screen streams - maybe too hairy)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=351355&aid=1339718&group_id=1355