From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org
Subject: Re: GUI Framework Options
Date: Sun, 14 Oct 2018 12:54:41 +0100 [thread overview]
Message-ID: <20181014125441.08c45cba3166f8a9573ac53d@gmail.com> (raw)
In-Reply-To: <20181012193835.4e16941b@capac>
On Fri, 12 Oct 2018 19:38:35 -0300
David Pirotte <david@altosw.be> wrote:
> Hi again,
>
> > ...
> > No I didn't. I do remember we talked about this, but I can't find the emails we've
> > exchanged about this, nor could I find a snipset to reproduce it (I must have lost
> > these emails): with absolutely no promise what so ever, please re-post the short
> > example you made at the time so we can reproduce it.
> > ...
>
> I found the thread that leaded to our conversation, and within it, here is the email
> containing yor example ...:
>
> https://lists.gnu.org/archive/html/guile-user/2016-02/msg00104.html
>
> I do not plan to work on this, but if anyone wants to fix it, well please do and let
> us know ...
I have looked at it a couple of times and given up. I have found the
guile-gnome wrapper impenetrable.
There are other things wrong with guile-gnome which makes it (in my
view) not especially usable. One which comes to mind is that
g-io-add-watch won't compile in user code, nor will much else of the
GIOChannel stuff, which is quite a fail if you want to write callbacks
for asynchronous i/o events using the glib main loop. There is a work-
around for the first of those (g-io-add-watch) but not (as far as I can
tell) for the other related issues (you cannot for example get a
GIOCondition status). This is a wrapper problem, possibly caused by the
introduction of the gio namespace in glib some years ago (which has
nothing to do with GIOChannel).
Chris
next prev parent reply other threads:[~2018-10-14 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.93.1538928024.28328.guile-user@gnu.org>
2018-10-07 18:53 ` GUI Framework Options Zelphir Kaltstahl
2018-10-08 16:20 ` Mike Gran
2018-10-08 19:12 ` David Pirotte
2018-10-08 21:06 ` Zelphir Kaltstahl
2018-10-08 22:55 ` Chris Vine
2018-10-12 17:56 ` David Pirotte
2018-10-12 22:38 ` David Pirotte
2018-10-14 11:54 ` Chris Vine [this message]
2018-10-08 21:05 ` Zelphir Kaltstahl
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181014125441.08c45cba3166f8a9573ac53d@gmail.com \
--to=vine35792468@gmail.com \
--cc=guile-user@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).