From: David Pirotte <david@altosw.be>
To: Michele Lindroos <keelefi@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: G-Golf - Help with ListView needed
Date: Thu, 9 Mar 2023 19:08:27 -0300 [thread overview]
Message-ID: <20230309190827.49275754@aicha> (raw)
In-Reply-To: <CAEvXz3R2PSx8BRqwXcoC4kP=onWp9giRcL68E-v_8-yL5_2iiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]
Hi Michele,
> ...
> You are right, I'm linking against gtk-4 shipped by the distribution
> I'm using. In this case, I'm on Ubuntu 22.04 which, at the time of
> writing this email, ships gtk-4 version 4.6.6.
> This leads me to a few follow-up questions:
> 1) I did build G-Golf using automake which should figure out all
> versions of the libraries I'm linking against.
there are two questions, here is the first answer:
G-Golf 'figures out' its own dependencies, and gtk is not a g-golf
dependency - note that this said, you need gtk+-3.0 to run make check,
but that is because it's needed to check the override mechanism, there
is 'no way out' - currently make checks also depends on clutter but i
am working to entirely remove the clutter dependency]
> Should an error have been raised when I called the incompatible
> constructor? Or maybe a print in the console log?
G-Golf can't do that, as by design, goops and the mop (meta object
protocl) allow 'other keyword(s)' (in a make call) - so this would
raise many false positive.
Also, as you may see in the peg-solitaire example, G-Golf users may
define GObject sub-classes that define direct slots that define
init-keyword, and those slots not registered as g-properties - ll
this is/are a feature, not a bug - this situation would also trigger
hundreds of false positive lanching then playing the game ...
You, as a G-Golf user and the author of a G-Golf based app, must know
your 'stuff', consult and double check the upstream lib doc ...
there is 'no way out either'.
> 2) Assuming I want to write shippable code, is it possible to know
> which gtk-4 version is being used and which constructor to call?
You will have to, assuming you use the autotool chain, add your own app
dependencies, like for example
PKG_CHECK_MODULES(GTK, gtk+-4.0 >= 4.6.6)
[or another version ofc, just an example ...
> 3) Is gtk-string-list unique in this regard, or are there also other
> classes which need to be instantiated using the non-idiomatic way?
Certainly not, but as i said, you write the app, you check (which is
easy really, and quite re insuring for your users ... as i said, you
must know your stuff, the upstream lib doc, its version, dperecation,
new interfces ... and try/doublecheck/verify when you face such a
situation ... there is no way out either, and be prepared, gtk and
libadwaita are in constant evolution ...
> Thanks a lot for all the help!
No problem,
Thanks for using G-Golf!
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-03-09 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 9:09 G-Golf - Help with ListView needed Michele Lindroos
2023-03-05 2:35 ` David Pirotte
2023-03-06 4:07 ` David Pirotte
2023-03-06 15:50 ` Michele Lindroos
2023-03-06 22:09 ` David Pirotte
2023-03-07 18:55 ` Michele Lindroos
2023-03-09 22:08 ` 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=20230309190827.49275754@aicha \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=keelefi@gmail.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).