From: Neil Jerram <neil@ossau.uklinux.net>
To: Alex Kim <theseven222@yahoo.com>
Cc: Bo Forslund <bo.forslund@abc.se>,
guile-gtk@sources.redhat.com, guile-user@gnu.org
Subject: Re: Newbie pleading for help...
Date: Wed, 20 Feb 2002 13:13:00 -0000 [thread overview]
Message-ID: <m3664r985j.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20020220172011.35235.qmail@web20407.mail.yahoo.com>
>>>>> "Alex" == Alex Kim <theseven222@yahoo.com> writes:
Alex> Then, I wanted to add event processing loop for the
Alex> GUI itself to respond to the mouse interaction so
Alex> that I can interactively modify the lines as needed.
Alex> As I described in the previous message, this
Alex> turned out to be very hard for me to achieve since two
Alex> event loops that never return are required (one for
Alex> gh_repl and the other for GUI).
Hi Alex,
I wrote a short essay on this once, but lost it when my box crashed;
but it may still be available in the Guile mail archive somewhere. I
think I called it "GUIfying the Guile REPL", so you could try
searching for that.
If you are happy to have the Guile REPL entry line in a Gtk widget
(rather than from the terminal that you ran the program from), then
you can do something very similar to my guile-gui package (available
from http://www.ossau.uklinux.net/guile/). If you need more help to
understand what this is done, I'd be happy to provide it.
One caveat with guile-gui is that I haven't tried running it since the
guile-gtk package (which you will also need) was at version 0.18; so
it might need some tweaking for the last guile-gtk.
Regards,
Neil
next prev parent reply other threads:[~2002-02-20 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C73B6EF.D482F76C@abc.se>
2002-02-20 9:20 ` Alex Kim
2002-02-20 9:48 ` Brett Viren
2002-02-20 12:46 ` Alex Kim
2002-02-20 13:02 ` Brett Viren
2002-02-23 23:48 ` Alex Kim
2002-02-20 13:13 ` Neil Jerram [this message]
2002-02-21 1:56 ` Hilaire Fernandes
2002-02-19 20:55 Alex Kim
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=m3664r985j.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bo.forslund@abc.se \
--cc=guile-gtk@sources.redhat.com \
--cc=guile-user@gnu.org \
--cc=theseven222@yahoo.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).