public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: wang cui <iucgnaw@msn.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Any suggestion about text-based GUI function?
Date: Thu, 05 Jul 2007 04:39:00 -0000	[thread overview]
Message-ID: <20070705043836.GA6444@ubuntu> (raw)
In-Reply-To: <BAY110-F344675F956AD790A874373A5020@phx.gbl>

On Thu, Jul 05, 2007 at 03:34:03AM +0000, wang cui wrote:
> Hi,
> 
> As we always provide console for user interaction. It's difficult for use 
> to remember and understand so many commands.
> 
> I'd like to provide a text-based GUI interface, a great example is Turbo C 
> program.
> 
> I did some work on my target, analysis user input(eg. arrow keys) from 
> terminal(HyperTerminal), and keep the terminal screen layout unchanged, but 
> update corresponding fields. Also automaticaly update statistic fields when 
> changed.
> I found it useful for newbie user.
> 
> Is there guide article or open-source library to help accomplish such 
> function?

You would like to read this nice article:
http://www-128.ibm.com/developerworks/library/pa-tams3/ 

Peter Seebach told about using BSD curses under eCos. AFAIK, there are 2
_main_ TUI libraries in open-source world. These are slang and ncurses.

But let think about an Expect (http://www.tcl.tk) too. Using Expect and
any TUI wrapper (I prefer `whiptail' on Linux), it isn't difficult to
write an interactive system is embedding no extra libraries in your eCos
programs. What do we need? That's just any CLI prompt.

regards,

-- Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2007-07-05  4:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  3:34 wang cui
2007-07-05  4:30 ` Paul D. DeRocco
2007-07-05  4:39 ` Sergei Gavrikov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070705043836.GA6444@ubuntu \
    --to=w3sg@softhome.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=iucgnaw@msn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).