Re: [Gterm-discuss] a small todo list
Brought to you by:
theosib
From: Jörg S. <joe...@we...> - 2002-12-11 10:15:25
|
On Wed, 11 Dec 2002 16:09:59 +0800 Zhang Le <ej...@pe...> wrote: > Hi all, > I write a small todo list here and hope you may have interest. It's a long > way to go anyway. Think so too. I hope to have a replacement for the FreeBSD kernel vt someday :-) > > A.GTerm core > 1. implement xterm extension such as setting application title , font change, > color change Add the "screen save"/ "screen read" extension. This is useful at least for mc. > 2. history review support > 3. cut/paste selection interface > 4. UTF-8/unicode wide char support This is interesting. This is useful. > > B.GTerm application > 1. split tty code into a separate component for easy maintain and porting I will do it this week. > 2. port to FreeBSD The same. Theosib, can you chance the project overview next week? ;-) > 3. add a scroll bar to history review > 4. add a config file for easy user configure I suggest a Makefile.config for things like CFLAGS, included by the main Makefile. Also Makefile.depend for finer dependencies. The compile time configuration goes into config.h(pp) to simplify later to autoconf. > 5. background image(may not be so useful) > 6. integrate with autoconf/automake build system This is a big thing. Let's start simple, at the moment this is not needed. > 7. XIM support [ Fingers scratching the head, trying to remember] OK. What is XIM useful for in a terminal emulator? > > I have already written some history review mode code in zhcon > project(sf.net/projects/zhcon). It will not be too difficult to port it to > gterm. But I can not find time to do it until March next year. So if you can > wait, I can do it then. > > BTW I find the CVS code does not have a consistent indent. Some use space, > some use tab char. It's common practice to use only white space to indent > code. So I suggest to use 4 white space to indent source code. > If you too use vim, add > /* > * vi:ts=4:shiftwidth=4:expandtab > * vim600:fdm=marker > */ > to source code is enough. We could also agree about same consistent astyle/indent command line. > -- > Sincerely yours, > Zhang Le Regards, Joerg Sonnenberger |