On Fri, 26 Apr 2019 at 18:38, Stefan Salewski wrote:
> On Fri, 2019-04-26 at 18:21 +0100, Emmanuele Bassi wrote:
> > It most definitely is not. The project is actively maintained, and it
> > recently got even a full description of the XML schema:
>
> That is interesting. Well 172 open issues
>
>
On Fri, 26 Apr 2019 at 18:13, Stefan Salewski wrote:
> On Fri, 2019-04-26 at 17:58 +0100, Emmanuele Bassi via gtk-list wrote:
> > Have you considered using the GObject introspection data that GTK
> > itself generates, instead of your custom parsing code?
>
> But a warning:
On Fri, 26 Apr 2019 at 17:46, vmagnin wrote:
> I am one of the main authors and administrators, working on the python
> script used to parse the GTK .h header files and generate the Fortran
> interfaces.
Have you considered using the GObject introspection data that GTK itself
generates, instea
Hi all;
next week, on May 1st, this list will be archived[0]. This means no new
subscriptions, and no new email.
If you have questions about GTK, GLib, and the rest of the core GNOME
development platform, you can use the Discourse[1] instance hosted on GNOME
infrastructure; we have a Platform/Cor
Thanks for your patience; it took me a while to get around answering this
email.
On Thu, 28 Mar 2019 at 09:34, David Pirotte wrote:
> Hello,
>
> > now that we've started migrating[0] GTK discussions from mailing lists
> over
> > to Discourse[1], we'd like to do the same for discussions on GTK la
Hi all;
now that we've started migrating[0] GTK discussions from mailing lists over
to Discourse[1], we'd like to do the same for discussions on GTK language
bindings.
For this reason we opened a new category:
https://discourse.gnome.org/c/platform/language-bindings
There are a few language-s
Hi all;
as announced in:
https://mail.gnome.org/archives/gtk-devel-list/2019-March/msg0.html
we have created a Discourse instance available at:
https://discourse.gnome.org
After testing it for the past couple of weeks, we're very satisfied with
how the platform behaves, so we are going
On Wed, 13 Mar 2019 at 16:16, Igor Korot wrote:
> >> How about porting recent GTK version to OpenVMS?
> >
> >
> > If you want to add a new platform to GTK, you will need to:
>
> Here is the problem - it is not a new port.
>
The last version of GTK+ on OpenVMS is GTK+1.x.
>
The last GTK 1.x rele
On Wed, 13 Mar 2019 at 15:53, Igor Korot wrote:
> Hi, Emmanuel et al,
>
> On Sun, Mar 10, 2019 at 4:38 AM Emmanuele Bassi via gtk-list
> wrote:
> >
> > Meta: having this discussion on gtk-list is probably the best example as
> to why we need to move to Discours
Thanks, very much appreciated!
Ciao,
Emmanuele.
On Wed, 13 Mar 2019 at 13:56, Kasper Peeters
wrote:
> > Care to file an issue:
> >
> > https://gitlab.gnome.org/Infrastructure/gtk-web
> >
> > to update the wording?
>
> Done, see
>
> https://gitlab.gnome.org/Infrastructure/gtk-web/merge_requ
On Sun, 10 Mar 2019 at 11:02, Kasper Peeters
wrote:
But for the 'big picture documentation', which includes up-to-date
> instructions on how to get it up and running on all platforms. Why
> gtk.org does not even seem to mention vpckg and Homebrew is a mystery
> to me, and seems easy to fix.
>
Ca
Meta: having this discussion on gtk-list is probably the best example as to
why we need to move to Discourse. Nobody involved with the development of
GTK even reads this list, except me, so you're never going to get more than
my opinion about it.
Meta × 2: while I am employed by the GNOME Foundati
Note: for those who prefer email, we've written down a handy guide on how
to use email with Discourse:
https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
Ciao,
Emmanuele.
On Fri, 1 Mar 2019 at 15:50, Emmanuele Bassi wrote:
> And, of course, I forgot the link: https://disc
And, of course, I forgot the link: https://discourse.gnome.org
Embarrassing.
Ciao,
Emmanuele.
On Fri, 1 Mar 2019 at 15:41, Emmanuele Bassi wrote:
> Hi all;
>
> after the discussion[1] last month, and the feedback received (both on
> list and off), we decided to trial a Discourse instance on t
Hi all;
after the discussion[1] last month, and the feedback received (both on list
and off), we decided to trial a Discourse instance on the GNOME
infrastructure.
The Platform/Core sub-category is meant to be used for all discussions
about GTK, GLib, GdkPixbuf, Pango, and other core libraries of
Hi;
Are you calling gtk_widget_show_all() on the Stack or Notebook, at any
point?
If you call show_all() on a container, all children will be marked as
visible; you need to use gtk_widget_set_no_show_all() if you don't want
this behaviour.
Ciao,
Emmanuele.
On Tue, 19 Feb 2019 at 12:14, Daniel
Thanks.
Sadly, there is just one person responsible for library-web, and he
maintains it on his spare time—which has gotten considerably smaller.
I'd be tempted to suggest the *mm bindings developers to use CI to generate
the documentation and publish it on the GitLab pages, like GTK does for its
On Thu, 14 Feb 2019 at 18:41, Kasper Peeters
wrote:
> TL;DR: can someone who is responsible or knows someone who is
> responsible for the developer API pages please read the text below,
> there is a serious issue with many GNOME libraries NOT having any API
> documentation online.
>
> Full story:
The list is not really dead, but nobody is required to give you an answer:
this is not a paid support channel.
If you're not getting answers it may be the case that you're doing
something that nobody else is doing.
Ciao,
Emmanuele.
On Wed, 13 Feb 2019 at 08:38, Giuseppe Torelli via gtk-list <
g
On Thu, 7 Feb 2019 at 13:16, Eric Williams via gtk-list
wrote:
> One benefit I find to mailing lists is that they are search engine
> indexed, meaning when I google a warning or assertion error I often get
> pointed to a mailing list thread that discusses the issue I am trying to
> fix.
>
> Being
More information on Discourse:
- About: https://www.discourse.org/about
- Features: https://www.discourse.org/features
Discourse is a forum software that has multiple ways to access it: web,
native apps, and email. It's not a mailing list software with a web
frontend.
The interesting (to me)
[Cross-posted to various relevant mailing lists; please, reply to
gtk-devel-list]
As part of an attempt at making GTK more friendly to newcomers, I and other
core developers were thinking of moving the mailing lists from the current
mailman installation to Discourse:
https://discourse.org/
Pos
On Wed, 16 Jan 2019 at 10:34, Nandakumar Edamana via gtk-list <
gtk-list@gnome.org> wrote:
> Is there a JSON-based UI description language (like XUL based on XML)?
> If so, is it supported by GTK+?
>
No. GTK only supports GtkBuilder UI descriptions, which use an XML subset:
https://developer.
On Tue, 2 Oct 2018 at 20:02, Giuseppe Torelli via gtk-list <
gtk-list@gnome.org> wrote:
> Thank you. Any other clue? The question is not interesting?
>
>
It's more of a problem of scope: we have no idea what your application
does, or how it uses GTK.
Are you drawing using GDK API instead of Cairo
On Mon, 20 Aug 2018 at 22:11, Alexander Medvednikov via gtk-list <
gtk-list@gnome.org> wrote:
> GTK draws things with Cairo, and if the graphics driver is installed,
> Cairo uses the OpenGL backend. Otherwise it uses software rendering via
> xlib.
>
> Is this correct?
>
No.
GTK does not use the
On Wed, 25 Jul 2018 at 12:44, Göran Hasse wrote:
> Hello!
>
> I try to write my own widget. For this a study gtkswitch.c/.h
> ( http://ftp.gnome.org/pub/gnome/sources/gtk+/3.22/gtk+-3.22.30.tar.xz )
>
> There is a function gtk_switch_get_type - but there is no
> implementation?
>
See G_DEFINE_TY
Hi;
virtual keyboards running outside of the windowing system platform as
clients do not use the XTest API — mostly because it's meant only for
testing X, and because it's only for X. Injecting synthetic events into the
windowing system is just not going to give you what you want, if what you
want
27 matches
Mail list logo
