From: Mike Gran <spk121@yahoo.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: [ANN] guile-gi v0.0.1 released
Date: Mon, 3 Jun 2019 07:46:48 -0700 [thread overview]
Message-ID: <20190603144648.GA7713@spikycactus.attlocal.net> (raw)
In-Reply-To: <874l59smoy.fsf@gnu.org>
On Sat, Jun 01, 2019 at 11:02:21AM +0200, Jan Nieuwenhuizen wrote:
>
> I've created a package description for Guix (see attached), with some
> patches (also attached).
>
> How is is that I overlooked this thread? I spent last Thursday --
> reluctantly -- adding webkitgtk bindings to guile-gnome and debugging
> an initial browser test. With Guile-GI it worked in minutes! :-)
>
> One of the patches adds the web browser example and the last one adds an
> editor example...but that segfaults in the key-press-event handler.
>
> I've just noticed test/closures.c -- is that intended for handlers like
> key-press-event; are they different from `clicked'?
This is me trying to explain to myself how the meta_marshaller was working
in PyGObject, on which much of this code is based.
>
> Patches also on my `wip' branch: https://gitlab.com/janneke/guile-gi.git
I am pleased and super embarrassed that someone has taken the time to
patch this code. It is really rough code. I had lost momentum on
this project, but, I'll try to get back to it.
Thanks for checking it out.
-Mike Gran
next prev parent reply other threads:[~2019-06-03 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181115144125.GA23468@joshua.dnsalias.com>
2019-06-01 9:02 ` [ANN] guile-gi v0.0.1 released Jan Nieuwenhuizen
2019-06-02 16:15 ` Ludovic Courtès
2019-06-02 18:22 ` Jan Nieuwenhuizen
2019-06-03 14:46 ` Mike Gran [this message]
2019-06-03 16:41 ` Jan Nieuwenhuizen
2019-06-04 14:45 ` Mike Gran
2019-06-04 19:47 ` Jan Nieuwenhuizen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603144648.GA7713@spikycactus.attlocal.net \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).