From: Jesper Juhl <jesper.juhl@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/3] [kconfig] Direct use of lxdialog routines by menuconfig
Date: Wed, 14 Dec 2005 23:57:18 +0100 [thread overview]
Message-ID: <9a8748490512141457g453178b4w5ab8537041fc3277@mail.gmail.com> (raw)
In-Reply-To: <20051212004606.31263.37616.stgit@machine.or.cz>
On 12/12/05, Petr Baudis <pasky@suse.cz> wrote:
> After three years, the zombie walks again! This patch (against the latest
> git tree) cleans up interaction between kconfig's mconf (menuconfig
> frontend) and lxdialog. Its commandline interface disappears in this patch,
> instead a .so is packed from the lxdialog objects and the relevant
> functions are called directly from mconf.
>
> In practice, this means that drawing on the screen is done with _MUCH_
> less overhead now, the screen updates are better optimalized as ncurses
> won't get reset everytime you display something, that also implies that
> the ugly screen flickering is done. As a cute side-effect, the dialogs
> are now rendered on the top of the menu or help panel. In the future,
> this also gives us much more freedom for enhancing the user interface.
>
> This opens space for plenty of cleanups of liblxdialog, removal of
> superfluous stuff and temporary files usage, etc.
>
> Compared to the previous version (from February 2003), this one should be
> less buggy (especially wrt. the escape character handling), should not
> crash while resizing and the resizing should have immediate effect
> (although things can still start looking ugly when you are resizing while
> not in a menu - to fix that properly, more liblxdialog integration is
> required). Also, the code is considerably simplified on few places.
>
> Signed-off-by: Petr Baudis <pasky@suse.cz>
I just gave it a very quick spin and I like it. Very nice.
It's definately a lot snappier, nice work.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-12-14 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 0:41 [PATCH 0/3] Link lxdialog with mconf directly Petr Baudis
2005-12-12 0:46 ` [PATCH 1/3] [kbuild] Allow building of standalone .so libraries Petr Baudis
2005-12-12 0:46 ` [PATCH 2/3] [kbuild] Possibility to sanely link against off-directory .so Petr Baudis
2005-12-12 0:46 ` [PATCH 3/3] [kconfig] Direct use of lxdialog routines by menuconfig Petr Baudis
2005-12-12 3:18 ` Kurt Wall
2005-12-12 11:20 ` Petr Baudis
2005-12-13 2:59 ` Kurt Wall
2005-12-14 22:18 ` Roman Zippel
2005-12-16 20:29 ` Sam Ravnborg
2005-12-14 22:57 ` Jesper Juhl [this message]
2005-12-12 19:14 ` [PATCH 0/3] Link lxdialog with mconf directly Sam Ravnborg
2005-12-12 20:08 ` Petr Baudis
2005-12-12 20:40 ` Sam Ravnborg
2005-12-16 21:26 ` Sam Ravnborg
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=9a8748490512141457g453178b4w5ab8537041fc3277@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.org \
/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 NNTP newsgroup(s).