From: Brett Viren <bv@bnl.gov>
To: Alex Kim <theseven222@yahoo.com>
Cc: guile-gtk@sources.redhat.com, guile-user@gnu.org
Subject: Re: Newbie pleading for help...
Date: Wed, 20 Feb 2002 13:02:00 -0000 [thread overview]
Message-ID: <15476.3822.73544.659246@minos.phy.bnl.gov> (raw)
In-Reply-To: <20020220204607.86460.qmail@web20404.mail.yahoo.com>
Alex Kim writes:
> The problem with doing everything in guile-gnome is
> that the toolkit contains too many stuffs already
> written in c, X, and gl. And I was hoping that some
> modification on GUI code will allow me to easily add
> more features written in guile (in the way plug-ins
> work; I thought this was what guile was for when I
> first started learning it---although I now realize it
> is much more than that).
Ah, okay. Also, I reread your past posting and saw you wanted to use
gh_repl(). I don't think this will work so well to combine gh_repl()
and some GUI's main loop (maybe it could be made to work with
guile-gtk, maybe not). So I would abandon gh_repl and instead read in
scheme using the native GUI's text widget and calling gh_eval_str() on
the result and/or load in the scheme as a file with gh_eval_file().
(Or, rather their scm_ equivalents, because I think gh_ interface is
going away sometime, but gh_ is all *I* know right now....)
I successfully used this in a C++/Gtkmm/Guile application that had to
handle interactive users as well as servicing network requests. BTW,
when passing unkown scheme code into guile, I used the _catch versions
of the functions so that a typo in the scheme code wouldn't bring down
the whole app.
> In the mean time, I will
> study your code to get better understaning in this
> world.
Well I am not a great scheme coder, so don't study it too hard! <grin>
Luck,
-Brett.
next prev parent reply other threads:[~2002-02-20 21:02 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 [this message]
2002-02-23 23:48 ` Alex Kim
2002-02-20 13:13 ` Neil Jerram
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=15476.3822.73544.659246@minos.phy.bnl.gov \
--to=bv@bnl.gov \
--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).