Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Xfce switch to python3
Date: Tue, 21 Jan 2020 06:03:58 +0100	[thread overview]
Message-ID: <20200121050358.4ls_q1N2LXvv4nWCKlZR0o8Sm4Jc6n0eMRxrL7isRn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17766@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3049 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/17766#issuecomment-576518424

Comment:
> As far as I can see those modules are not for the interface designer,
> but rather they contain widget implementations that can be used
> at runtime by applications _as well as the designer_, same with the xfce plugin.

I don't think so,
Let's take libxfce4uiglade2.so as an example, it's compiled from a single C source file,
and contains only 3 functions:
```
void       glade_xfce_titled_dialog_post_create        (GladeWidgetAdaptor *adaptor,
                                                        GObject            *object,
                                                        GladeCreateReason   reason);
GtkWidget *glade_xfce_titled_dialog_get_internal_child (GladeWidgetAdaptor *adaptor,
                                                        GtkDialog          *dialog,
                                                        const gchar        *name);
GList     *glade_xfce_titled_dialog_get_children       (GladeWidgetAdaptor *adaptor,
                                                        GtkDialog          *dialog);
```
Which is used by glade
```
<?xml version="1.0" encoding="UTF-8"?>
<glade-catalog version="4.12.0" supports="gtkbuilder" name="libxfce4ui-2" library="xfce4uiglade2" domain="glade3" depends="gtk+" book="xfce4">
  <glade-widget-classes>
    <glade-widget-class name="XfceTitledDialog" generic-name="xfce-titled-dialog" title="Titled Dialog">
      <post-create-function>glade_xfce_titled_dialog_post_create</post-create-function>
      <get-internal-child-function>glade_xfce_titled_dialog_get_internal_child</get-internal-child-function>
      <get-children-function>glade_xfce_titled_dialog_get_children</get-children-function>
      <properties>
        <property translatable="True" ignore="False" id="subtitle" name="Subtitle"></property>
        <property translatable="True" ignore="False" id="title"/>
        <property ignore="True" id="icon"/>
        <property themed-icon="True" ignore="False" id="icon-name"/>
      </properties>
    </glade-widget-class>
  </glade-widget-classes>
  <glade-widget-group name="xfce4-widgets" title="Xfce 4 Widgets">
    <glade-widget-class-ref name="XfceTitledDialog"/>
  </glade-widget-group>
</glade-catalog>
```
as described by: https://developer.gnome.org/gladeui/stable/catalogintro.html

As far as I can tell, those functions are used to tell glade3
 the supported properties of XfceTitledDialog.


> I.e. the modules are loaded and used by `libgladeui`, which exposes them both to the interface designer itself as well as applications with interfaces designed using GLADE.

I strongly believe that the application itself uses the Gtk+ derived Widget,
those modules were there to tell glade their supported properties.

Anyway, glade3 also ships `./usr/lib/glade/modules/libgladegtk.so` to assist
designer works with gtk+, we don't need it to use gtk+ widget, right?


  parent reply	other threads:[~2020-01-21  5:03 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25  2:36 [PR PATCH] " voidlinux-github
2019-12-25  8:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-25 16:01 ` voidlinux-github
2019-12-25 21:18 ` voidlinux-github
2019-12-26 13:27 ` voidlinux-github
2019-12-26 13:27 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-26 14:23 ` voidlinux-github
2019-12-26 14:40 ` voidlinux-github
2019-12-26 14:42 ` voidlinux-github
2019-12-27 13:01 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-01  6:59 ` voidlinux-github
2020-01-02 12:50 ` voidlinux-github
2020-01-06 23:53 ` voidlinux-github
2020-01-07  0:06 ` voidlinux-github
2020-01-07 14:04 ` voidlinux-github
2020-01-11  2:41 ` voidlinux-github
2020-01-18 10:07 ` voidlinux-github
2020-01-18 10:40 ` voidlinux-github
2020-01-18 11:16 ` voidlinux-github
2020-01-18 14:03 ` voidlinux-github
2020-01-18 23:47 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-18 23:48 ` voidlinux-github
2020-01-18 23:58 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-19 15:00 ` voidlinux-github
2020-01-19 15:00 ` voidlinux-github
2020-01-20  3:06 ` voidlinux-github
2020-01-20  3:09 ` voidlinux-github
2020-01-20 13:26 ` voidlinux-github
2020-01-20 13:36 ` voidlinux-github
2020-01-20 14:14 ` voidlinux-github
2020-01-20 14:26 ` voidlinux-github
2020-01-20 14:39 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 14:45 ` voidlinux-github
2020-01-20 14:45 ` voidlinux-github
2020-01-20 14:55 ` voidlinux-github
2020-01-20 15:04 ` voidlinux-github
2020-01-20 15:04 ` voidlinux-github
2020-01-20 15:06 ` voidlinux-github
2020-01-20 15:10 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 15:27 ` voidlinux-github
2020-01-20 15:32 ` voidlinux-github
2020-01-21  4:58 ` voidlinux-github
2020-01-21  4:59 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-21  5:03 ` voidlinux-github [this message]
2020-01-21  5:09 ` voidlinux-github
2020-01-22  3:59 ` voidlinux-github
2020-01-22  4:01 ` voidlinux-github
2020-01-22  4:04 ` voidlinux-github
2020-01-30  2:35 ` voidlinux-github
2020-01-30 12:22 ` voidlinux-github
2020-02-03  2:47 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-03  2:47 ` voidlinux-github
2020-02-03  2:48 ` voidlinux-github
2020-02-03  2:48 ` voidlinux-github
2020-02-03 10:30 ` voidlinux-github
2020-02-03 10:32 ` voidlinux-github
2020-02-03 10:33 ` voidlinux-github
2020-02-03 13:09 ` voidlinux-github
2020-02-03 13:14 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-04  1:08 ` voidlinux-github
2020-02-04  2:59 ` voidlinux-github
2020-02-04  7:35 ` voidlinux-github
2020-02-04  7:59 ` voidlinux-github
2020-02-04 12:40 ` voidlinux-github
2020-02-04 13:17 ` voidlinux-github
2020-02-04 20:11 ` voidlinux-github
2020-02-05 15:01 ` [PR PATCH] [Closed]: " voidlinux-github

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200121050358.4ls_q1N2LXvv4nWCKlZR0o8Sm4Jc6n0eMRxrL7isRn0@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).