From: David Pirotte <david@altosw.be>
To: ludo@gnu.org (Ludovic Courtès), guile-devel <guile-devel@gnu.org>,
g-wrap-dev <g-wrap-dev@nongnu.org>
Subject: Re: g-wrap: reference manual updated
Date: Mon, 23 Jun 2014 16:51:14 -0300 [thread overview]
Message-ID: <20140623165114.5b98f063@capac> (raw)
In-Reply-To: <874mzbn76m.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 2177 bytes --]
Hello Ludovic,
> Congrats for all this work. ;-)
Thanks. This manual still need a review, related to garbage collection [and
smob maybe?]: all occurrences in this manual still refer to the previous garbage
collector...
> I think this should go to G-Wrap’s mailing list:
> https://lists.nongnu.org/mailman/listinfo/g-wrap-dev
Done.
> And I think you should ask for commit access for Guile-GNOME & co.
I have write access to guile-gnome[clutter] already, thanks, and sent a [pending]
request for guile-cairo. I don't pretend to work on guile-cairo right now, it's
fine as it is [we bind 1.10.2] and cairo 1.12.x does not bring anything reaaaaallly
fancy.
I am almost done with the actual binding for guile-gnome: this is _not_ an update of
the bindings per se: the idea is [while learning] to release a guile-gnome
[platform] 2.16.3 version which strictly depends on guile 2, fixing tips and bits
and if possible getting rid of all [or almost all] warnings @ compile time [because
it scares end users :)]. Then as time allows _and_ as requested along the way by
guile-clutter binding updates, I'd like to slowly update guile-gnome glib and gobject
bindings [from 2.16 to 2.40 for glib...]
I am almost done with guile-clutter 1.12.2, but has you all know by now, I still
have to properly understand a couple of things related to g-wrap... hence this
work. I should read the manual now, haha!
We have 2 major issues using guile-clutter: (1) spawning a server [for debug
purposes for example] almost systematically [but not always] triggers
gobject-CRITICAL errors leading to guile crashes, and (2), there is a
synchronization problem between cairo and clutter [(invalidate (get-content
a-clutter-canvas-instance)) _does_ trigger the 'draw signal and calls your drawing
method, _but_ the canvas remains or empty or redraw the cairo 'object' as it was at
first invalidate call. I'll email details about that as soon as possible, but
wanted to here here about the status,... the 2 above mentioned problems could well
exists the exact same way strictly using guile-gnome [no clutter], still have to
try].
Cheers,
David
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
g-wrap-dev mailing list
g-wrap-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/g-wrap-dev
prev parent reply other threads:[~2014-06-23 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 8:52 g-wrap: reference manual updated David Pirotte
[not found] ` <874mzbn76m.fsf@gnu.org>
2014-06-23 19:51 ` David Pirotte [this message]
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=20140623165114.5b98f063@capac \
--to=david@altosw.be \
--cc=g-wrap-dev@nongnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).