public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Alex Kim <theseven222@yahoo.com>
To: guile-gtk@sources.redhat.com
Cc: theseven222@yahoo.com
Subject: Newbie pleading for help...
Date: Tue, 19 Feb 2002 20:55:00 -0000	[thread overview]
Message-ID: <20020220045507.48061.qmail@web20403.mail.yahoo.com> (raw)

Dear guile (and guile-gtk) experts,

I understand that my question may irritate some of you
since it has been discussed here before. Nevertheless,
I am asking the question with desperation and as a 
last resort.  Many apologies.

I was given a task a couple of months ago.  After a
long serious thinking, I came up with an idea which
made use of a lot of stack and list operations (which
scheme is good at) and wanted to verify my idea as
quickly as possible.  Fortunately (or unfortunately, I
can't say for sure yet), I know just enough scheme to
write moderate size programs. So, I started coding in
scheme.


My intension was to implement the idea in guile scheme
and the GUI in c with X or gtk providing one simple
line drawing function for guile to call so that I can
draw lines as they are computed from scheme code
(similar to tortoise example). And it worked great.

Then, I wanted to add event processing to the GUI and
this is where I got stuck---it also required its own
event loop in addition to gh_repl.  At first, I
naively thought I could resolve the problem using
pthread, which didn't work.  With pitiful and (of
course) unsuccessful debugging of many days, I looked
up the list's archive and found out that the question
has been discussed previously and someone successfully
solved the problem using event-repl stuff coming with
guile-gtk.  Nevertheless, with my short knowledge of
guile, the discussions were hard to follow and I ended
up with a conclusion of rewriting the whole thing in
c.

However, I still desperately want to stay with scheme
since it will make further improvement of my idea
extremely easier.  So, before I begin to rewriting, I
thought I might ask you, the guile experts, for help
as a last resort.  Would anyone out there generously
provide me some pointers or simple example codes that
work just like tortoise example, but with added event
handling ability (either X or gtk)?  I would be very
grateful to you.

Please accept my sincere apology if you got upset by
my posting of what has been discussed before.
Thank you very much.

Sincerely,







__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com

             reply	other threads:[~2002-02-20  4:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 20:55 Alex Kim [this message]
     [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
2002-02-21  1:56   ` Hilaire Fernandes

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=20020220045507.48061.qmail@web20403.mail.yahoo.com \
    --to=theseven222@yahoo.com \
    --cc=guile-gtk@sources.redhat.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).