unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 4 Jun 2019 07:45:01 -0700	[thread overview]
Message-ID: <20190604144501.GA14845@spikycactus.attlocal.net> (raw)
In-Reply-To: <87blzehb93.fsf@gnu.org>

On Mon, Jun 03, 2019 at 06:41:44PM +0200, Jan Nieuwenhuizen wrote:
> Mike Gran writes:
> 
> Hi!
> 
...

> 
> Ah, that makes sense.  I started playing with it and learned one or two
> things, until i found src/gclosure.c :-)
> 
> Have you seen the gclosure implementation in guile-gnome, would that be
> any help?
> 
>     https://git.savannah.gnu.org/cgit/guile-gnome.git/tree/glib/gnome/gobject/gclosure.scm

Both guile-gnome and my hack have two parts
- an introspection layer
- a gobject-to-guile binding

I had a chat with Wingo at the last FOSDEM, and he thinks the
gobject-to-guile binding could be reused, and that I could just swap
the gwrap GTK+2 introspection layer with a GObject introspection
layer.  I began analyzing that path a few months before life
intervened.

> 
> I'm quite new to all this, I cannot see the great difference in gtk+2
> and gtk+3 here, even...
> 
> >> Patches also on my `wip' branch: https://gitlab.com/janneke/guile-gi.git

I incorporated these, and fixed the bug that caused your editor example
to fail.  Thanks!

Thanks,
Mike

  reply	other threads:[~2019-06-04 14:45 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
2019-06-03 16:41     ` Jan Nieuwenhuizen
2019-06-04 14:45       ` Mike Gran [this message]
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=20190604144501.GA14845@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).