Re: Demo/Sample for drag and drop

I found these quite good (even though I wasn't using ListBox; they can be generalised) https://blog.gtk.org/2017/04/23/drag-and-drop-in-lists/ https://blog.gtk.org/2017/06/01/drag-and-drop-in-lists-revisited/ ___ gtk-devel-list mailing list gtk-devel-li

Re: Gtk::Widget::is_mapped ()

On 03/03/2019 16:10, Paul Davis wrote: John should really know that there's code to do this (to the best extent possible) within the Ardour source code at libs/gtkmm2ext/visibility_tracker.cc :))) Hi Paul - that's in fact what I'm investigating There's a new object called 'PluginDspLo

Re: Gtk::Widget::is_mapped ()

On Sun, Mar 3, 2019 at 9:21 AM Emmanuele Bassi wrote: > No, it's not. The issue is not GTK: it's the windowing system. > > With the advent of compositing, all windows are "visible" all the time, > from a toolkit perspective. The compositor is responsible for building > what's presented to the use

Re: Gtk::Widget::is_mapped ()

No, it's not. The issue is not GTK: it's the windowing system. With the advent of compositing, all windows are "visible" all the time, from a toolkit perspective. The compositor is responsible for building what's presented to the user. For example: are windows fully visible when doing an "exposé"-

Re: Gtk::Widget::is_mapped ()

On Sun, Mar 3, 2019 at 6:26 AM Emmanuele Bassi via gtk-devel-list < gtk-devel-list@gnome.org> wrote: > On Sun, 3 Mar 2019 at 12:58, John Emmas wrote: > >> > For example... let's say the widget is a top-level window. If it's >> currently displayed on screen but there's some other window hiding it

Re: Gtk::Widget::is_mapped ()

On Sun, 3 Mar 2019 at 12:58, John Emmas wrote: > On 03/03/2019 11:22, Emmanuele Bassi wrote: > > On Sun, 3 Mar 2019 at 11:09, John Emmas wrote: > >> Sorry to ask a dumb question... >> >> What does it mean if a widget is "mapped" ? >> > > It means that: > > - the widget is visible > - the widge

Re: Gtk::Widget::is_mapped ()

On 03/03/2019 11:22, Emmanuele Bassi wrote: On Sun, 3 Mar 2019 at 11:09, John Emmas > wrote: Sorry to ask a dumb question... What does it mean if a widget is "mapped" ? It means that:  - the widget is visible  - the widget is realized  - all its ancest

Re: Gtk::Widget::is_mapped ()

On Sun, 3 Mar 2019 at 11:09, John Emmas wrote: > Sorry to ask a dumb question... > > What does it mean if a widget is "mapped" ? > It means that: - the widget is visible - the widget is realized - all its ancestors up to the top level window are mapped Only mapped widgets are drawn and can

Re: Discourse instance

On Sat, 2019-03-02 at 21:07 +, Philip Withnall wrote: > Well, I suspect LRN would probably appreciate a ‘windows’ tag. I've added a topic in Site Suggestions for these to collate them :) Neil -- Neil McGovern Executive Director, The GNOME Foundation _

Re: Discourse instance

On Fri, 2019-03-01 at 19:34 +, Neil McGovern wrote: > On Fri, 2019-03-01 at 20:37 +0300, LRN via gtk-devel-list wrote: > > Well, what i mean is that i'd like to be able to be notified of > > topics that are > > relevant to me, and one way to do that is to allow topics to be > > tagged and > > a

Re: Discourse instance

On Fri, 01 Mar 2019 19:14:21 +0100, Ernestas Kulik wrote: > I haven’t gone through the tutorial with discobot, but seems that 2FA > is not going to work with LDAP logins, right? I've got 2FA set up, but was only asked for my password. -- begin .sig < Jernej Simončič ><>◊<>< jernej|s-ng at eter

Re: Discourse instance

On Fri, 2019-03-01 at 19:34 +, Neil McGovern wrote: > Ah, yes. You can do that! > I'm also aware of the irony of replying here, rather than on the discourse instance so others can see and learn. We have a site feedback category :) Neil -- Neil McGovern Executive Director, The GNOME Foundat

Re: Discourse instance

On Fri, 2019-03-01 at 19:14 +0100, Ernestas Kulik wrote: > I haven’t gone through the tutorial with discobot, but seems that 2FA > is not going to work with LDAP logins, right? Yes... in a way. Turning on 2FA requires a password and with LDAP logins, Discourse has a null password for your account.

Re: Discourse instance

On Fri, 2019-03-01 at 20:37 +0300, LRN via gtk-devel-list wrote: > Well, what i mean is that i'd like to be able to be notified of > topics that are > relevant to me, and one way to do that is to allow topics to be > tagged and > allow people to subscribe to tags. Ah, yes. You can do that! http

Re: Discourse instance

On Fri, 2019-03-01 at 15:41 +, Emmanuele Bassi via gtk-devel-list wrote: > Hi all; Hey. > 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 me

Re: Discourse instance

On 01.03.2019 20:17, Neil McGovern wrote: > On Fri, 2019-03-01 at 19:52 +0300, LRN via gtk-devel-list wrote: >> On 01.03.2019 18:41, Emmanuele Bassi via gtk-devel-list wrote: >>> Feedback is very much appreciated. >>> >> >> Need moar tags! >> > > Tag suggestions welcome :) > Well, what i mean is

Re: Discourse instance

On Fri, 2019-03-01 at 19:52 +0300, LRN via gtk-devel-list wrote: > On 01.03.2019 18:41, Emmanuele Bassi via gtk-devel-list wrote: > > Feedback is very much appreciated. > > > > Need moar tags! > Tag suggestions welcome :) Neil -- Neil McGovern Executive Director, The GNOME Foundation ___

Re: Discourse instance

On 01.03.2019 18:41, Emmanuele Bassi via gtk-devel-list wrote: > Feedback is very much appreciated. > Need moar tags! signature.asc Description: OpenPGP digital signature ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org

Re: Discourse instance

On Fri, 2019-03-01 at 15:41 +, Emmanuele Bassi via gtk-devel-list wrote: > 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. Additionally, if you're a Foundation member, you can log in

Re: Discourse instance

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

Re: Discourse instance

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

Re: Discourse instance

Since you forgot the link... https://discourse.gnome.org/ -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Fri, Mar 1, 2019, 9:42 AM Emmanuele Bassi via gtk-devel-list < gtk-devel-list@gnome.org> wrote: > Hi all; > > after the discu

Re: Glib::Threads:Private

On 20/02/2019 15:26, Paul Davis wrote: On Wed, Feb 20, 2019 at 1:17 AM John Emmas > wrote: I realise it's a deprecated interface but can anyone explain what Glib::Threads:Private does? [...] It means that each thread that accesses the variable

Re: Glib::Threads:Private

On Wed, Feb 20, 2019 at 1:17 AM John Emmas wrote: > I realise it's a deprecated interface but can anyone explain what > Glib::Threads:Private does? > > Does it guarantee that 'SomeObject' can only be accessed by code running > in a particular thread? And if so, does it do that by creating a > sp

Re: Project rename to "GTK"

On Wed, Feb 6, 2019 at 10:23 AM Owen Taylor wrote: > > On Wed, Feb 6, 2019 at 5:04 AM Emmanuele Bassi via gtk-devel-list > wrote: > > > > Hi all; > > > > tl;dr: GTK is GTK, not GTK+. The documentation has been updated, and the > > pkg-config file for the future 4.0 major release is now called "g

Re: Moving from mailing lists to Discourse

On Sat, 2019-02-09 at 02:15 +0200, makep...@firemail.cc wrote: > > open an issue for Gtk by > > emailing a specific email address on GitLab > > GNOME's instance seem to disallow creating issues by email. GitLab > itself, if configured with sub-addressing, generates a private email > address for

Re: Moving from mailing lists to Discourse

open an issue for Gtk by emailing a specific email address on GitLab GNOME's instance seem to disallow creating issues by email. GitLab itself, if configured with sub-addressing, generates a private email address for issues when you sign in and visit a repository page: https://docs.gitlab.co

Re: Moving from mailing lists to Discourse

On Pá, úno 8, 2019 at 11:53 PM, Reuben Rissler wrote: Thanks. But it probably isn't possible to open an issue for Gtk by emailing a specific email address on GitLab, or am I wrong? Only in Enterprise Edition Premium: https://gitlab.com/help/user/project/service_desk

Re: Moving from mailing lists to Discourse

On 02/08/2019 04:37 PM, makep...@firemail.cc wrote: So let me get this straight, GitLab has a feature where an ordinary user can setup his GitLab account to email him every time a new issue is created? It's on the repo page, behind the bell icon, to the left of the star. Visible after signi

Re: Moving from mailing lists to Discourse

So let me get this straight, GitLab has a feature where an ordinary user can setup his GitLab account to email him every time a new issue is created? It's on the repo page, behind the bell icon, to the left of the star. Visible after signing in. To be honest, I'd rather hide the stars and make

Re: Moving from mailing lists to Discourse

On Fri, 2019-02-08 at 11:07 +, Emmanuele Bassi via gtk-devel-list wrote: > > > In general, mailman3 + hyperkitty is a somewhat good upgrade on > mailman2 (even though I still prefer the old archive pages compared > to hyperkitty; I've been going through those *a lot* for my "History > of GNOM

Re: Moving from mailing lists to Discourse

On 02/08/2019 12:45 PM, makep...@firemail.cc wrote: ardour LMMS moved handling of support requests and conversations from their mailing list to GitHub issues and it works. Using GNOME's GitLab as the single place for discussions can also be considered an alternative. One can respond to i

Re: Moving from mailing lists to Discourse

> ardour LMMS moved handling of support requests and conversations from their mailing list to GitHub issues and it works. Using GNOME's GitLab as the single place for discussions can also be considered an alternative. One can respond to issues via email, and email is how I get my notifications

Re: Moving from mailing lists to Discourse

> - Hyperkitty's UX is confusing, cluttered to the point of being unhelpful Would benefit from examples of clutter. Opened home page, saw lists. Opened list, saw threads. Opened thread, saw replies and a new reply link. And some buttons for permalink, rating, archive and stats. Basic features

Re: Moving from mailing lists to Discourse

On Fri, Feb 8, 2019 at 7:33 AM Emmanuele Bassi via gtk-devel-list < gtk-devel-list@gnome.org> wrote: > > As for the subscription: Discourse supports multiple identity > providers—Google, Facebook, Instagram, Twitter, Yahoo, and GitHub are all > supported, and there's a plugin available for GitLab

Re: Moving from mailing lists to Discourse

On Wed, 6 Feb 2019 at 12:19, Emmanuele Bassi wrote: > > The main differences are that you’d need a different subscription account > than the existing one, and that you wouldn’t have the weekly digests, as > far as I can see. > It turns out I was wrong: Discourse has "weekly summaries" as well.

Re: Moving from mailing lists to Discourse

On Thu, 7 Feb 2019 at 00:54, wrote: > > We already looked at Hyperkitty, and found it fairly limited in > > functionality. Avoiding Hyperkitty is what led us to Discourse in the > > first place. > Can you link that discussion please? It was on IRC and in person discussions, and private emails b

Re: Moving from mailing lists to Discourse

> you would largely only use the web UI to sign up or change your settings. What about reading the history? I mostly end up on mailing lists web UI by following links from web searches and bug trackers. ___ gtk-devel-list mailing list gtk-devel-list@g

Re: Moving from mailing lists to Discourse

> hiding things that previously were obvious and made inaccessible without > scripting overhead > enabled, overabundant whitespace, tiny gray text, short lists where 5X as > many would otherwise fit. All these points that you make apply to Discourse. Its client side seems entirely JS and does

Re: Moving from mailing lists to Discourse

As has been mentioned, Discourse allows you to receive and via email, you would largely only use the web UI to sign up or change your settings. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Wed, Feb 6, 2019, 11:25 PM Felix Miata via

Re: Moving from mailing lists to Discourse

Emmanuele Bassi via gtk-devel-list composed on 2019-02-06 12:46 (UTC+0100): > Are there any objections? Did somebody already try out Discourse and has > opinions about it that they want to share with the community? As happened when various mozilla dev mailing lists moved to discourse, I ceased h

Re: Moving from mailing lists to Discourse

makep...@firemail.cc composed on 2019-02-07 02:54 (UTC+0200): >> We already looked at Hyperkitty, and found it fairly limited in >> functionality. Avoiding Hyperkitty is what led us to Discourse in the >> first place. > Can you link that discussion please? I'm interested what newcomers want > to

Re: Moving from mailing lists to Discourse

Hmm, unfortunately it was over some scattered IRC messages, I can try and find them in the logs if you like. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Wed, Feb 6, 2019, 8:38 PM wrote: > > I know someone who set up HyperKitty,

Re: Moving from mailing lists to Discourse

On Wed, 6 Feb, 2019 at 10:46 PM, Emmanuele Bassi via gtk-list wrote: 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: Possibly s

Re: Moving from mailing lists to Discourse

I know someone who set up HyperKitty, it was a nightmare How so? Can you link their blog post? I'm not its user or developer, I want to better understand the software choice. ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome

Re: Moving from mailing lists to Discourse

I know someone who set up HyperKitty, it was a nightmare and still is a nightmare. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Wed, Feb 6, 2019, 6:54 PM wrote: > > We already looked at Hyperkitty, and found it fairly limited in

Re: Moving from mailing lists to Discourse

We already looked at Hyperkitty, and found it fairly limited in functionality. Avoiding Hyperkitty is what led us to Discourse in the first place. Can you link that discussion please? I'm interested what newcomers want to do such that Hyperkitty doesn't let. Negatives of Discourse: loads slower,

Re: Moving from mailing lists to Discourse

On Wed, 2019-02-06 at 12:46 +0100, Emmanuele Bassi via gtk-devel-list wrote: > [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 l

Re: Moving from mailing lists to Discourse

As a side note, Python has also opened a Discourse instance (in addition to their Zulip experiment), and the results have pretty much been positive. I've also been on Fedora's for quite some time, and it's great. On Wed, Feb 6, 2019 at 5:46 AM Emmanuele Bassi via gtk-devel-list < gtk-devel-list@gn

Re: Moving from mailing lists to Discourse

Hi all, I'm very much in favor! Being able to still use e-mail while also having a convenient and pretty-looking interface is something I look *really* forward to. My only question is: what happens to the old archives? Do we keep them online as-is, or is there a plan to also migrate them? The for

Re: Project rename to "GTK"

On Wed, Feb 6, 2019 at 5:04 AM Emmanuele Bassi via gtk-devel-list wrote: > > Hi all; > > tl;dr: GTK is GTK, not GTK+. The documentation has been updated, and the > pkg-config file for the future 4.0 major release is now called "gtk4" > > over the years, we had discussions about removing the "+" f

Re: Moving from mailing lists to Discourse

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)

Re: Moving from mailing lists to Discourse

Emmaneule, at ardour.org, we recently switched from using Drupal forums to Discourse. The results have been delightful. We managed to get single sign on integration with our existing site working, which was important for us, but probably not so much for a GTK Discourse. More notably, once you figu

Re: Moving from mailing lists to Discourse

On Wed, 6 Feb 2019 at 15:11, Charles Lindsey wrote: > > > On 06/02/2019 11:46, Emmanuele Bassi via gtk-devel-list wrote: > > [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

Re: Moving from mailing lists to Discourse

On 06/02/2019 11:46, Emmanuele Bassi via gtk-devel-list wrote: [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 curre

Re: Moving from mailing lists to Discourse

Hi; On Wed, 6 Feb 2019 at 13:10, Reuben Rissler wrote: > > To introduce myself, I only am using Gtk for 3 years, but really like > the infrastructure / people / open source surrounding Gtk. I am > sometimes seen as 'theGtknerd'. > > > On 02/06/2019 06:46 AM, Emmanuele Bassi via gtk-devel-list wr

Re: Moving from mailing lists to Discourse

To introduce myself, I only am using Gtk for 3 years, but really like the infrastructure / people / open source surrounding Gtk. I am sometimes seen as 'theGtknerd'. On 02/06/2019 06:46 AM, Emmanuele Bassi via gtk-devel-list wrote: The GTK project would have various sub-topics, mostly arou

Re: Quartz Coordinates

On Tue, Nov 20, 2018 at 8:06 AM John Ralls wrote: > I’m working on GdkQuartz to bring it up to date with the rest of Gdk. I’m > starting with GdkDisplay and GdkMonitor mostly because of > https://gitlab.gnome.org/GNOME/gtk/issues/1312. This question may also > bear upon https://gitlab.gnome.org/G

Re: How to set style in a GTK+ 2 widget's realize function?

I can't answer your question. But I can say that we never use gtk_style*. Instead we just parse the RC file that includes "widget/style" associations, and then we use gtk_widget_set_name() on our widgets to get them to use the right style. On Fri, Nov 16, 2018 at 5:32 AM Brent W. Baccala wrote:

Re: GdkScreen size-changed and gdk_monitor_get_workarea problem

Hi Florian, On 8/11/18 1:41 pm, Florian Müllner wrote: > On Thu, Nov 8, 2018 at 12:35 PM Sebastian Geiger (Lanoxx) > wrote: >> >> I was able to resolve the issue yesterday, and found that it was not >> directly a Problem of GTK+. > > To some extent it is, I don't think its API currently allows w

Re: GdkScreen size-changed and gdk_monitor_get_workarea problem

On Thu, Nov 8, 2018 at 12:35 PM Sebastian Geiger (Lanoxx) wrote: > > I was able to resolve the issue yesterday, and found that it was not > directly a Problem of GTK+. To some extent it is, I don't think its API currently allows what you are trying to do. On X11, the WM is a client like your app

Re: GdkScreen size-changed and gdk_monitor_get_workarea problem

On Thu, 2018-11-08 at 12:34 +0100, Sebastian Geiger (Lanoxx) wrote: > Dear Bastien, > > thanks for the reply. I will attach a sample next time. > > My App runs with the X11 backend. > > I was able to resolve the issue yesterday, and found that it was not > directly a Problem of GTK+. > > The p

Re: GdkScreen size-changed and gdk_monitor_get_workarea problem

Dear Bastien, thanks for the reply. I will attach a sample next time. My App runs with the X11 backend. I was able to resolve the issue yesterday, and found that it was not directly a Problem of GTK+. The problem is, that the window manager computes the workarea asynchronosly, presumably it

Re: GdkScreen size-changed and gdk_monitor_get_workarea problem

On Tue, 2018-11-06 at 21:35 +0100, Sebastian Geiger (Lanoxx) wrote: > Hi Gtk developers, > > I am experiencing a wired issue and I am wondering if I am using the > API > in a wrong way of if there is a problem with Gtk. On Wayland or X11? > gdk_display_get_monitor_at_point and then gdk_monitor

Re: Translating enum values in schema

On Sat, 2018-09-15 at 16:25 +0200, rastersoft wrote: > Hi all: > I'm doing an schema for gsettings. This is part of it: > > > > > > > > id="org.gnome.shell.extensions.desktop-icons" gettext- > domain="desktop-icons"> > > "

Re: An alternative to gdk-pixbuf

On 09/15/18 10:48 AM, John Emmas wrote: On 15/09/2018 12:07, Magnus Bergman wrote: Some mismatch in versions of libtiff could for example be a reason. Otherwise you should probably file a bug report with more information (perhaps to your distribution firstly). Do you happen to know if the tif

Re: An alternative to gdk-pixbuf

On 16/09/2018 11:18, Emmanuele Bassi wrote: The correct way to report issues for gdk-pixbuf: 1. use the issue tracker: https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/new Thanks Emmanuele - done! ___ gtk-devel-list mailing list gtk-devel-list@gn

Re: An alternative to gdk-pixbuf

On Sun, 16 Sep 2018 at 10:47, John Emmas wrote: > On 15/09/2018 18:48, John Emmas wrote: > > > > Do you happen to know if the tiff library has its own mailing list? I > > haven't had much success in finding one > > > > In fact I'll need the mailing list for gdk-pixbuf now - except that I > ca

Re: An alternative to gdk-pixbuf

On 15/09/2018 18:48, John Emmas wrote: Thanks Magnus. I've a feeling that the problem might come down to struct alignment. No, I was wrong about that. I've tracked the problem to commit #ce52cefbbc in gdk-pixbuf (which brings me to the 2nd problem...) On 15/09/2018 18:48, John Emmas w

Re: An alternative to gdk-pixbuf

On 15/09/2018 12:07, Magnus Bergman wrote: Some mismatch in versions of libtiff could for example be a reason. Otherwise you should probably file a bug report with more information (perhaps to your distribution firstly). Thanks Magnus.  I've a feeling that the problem might come down to struc

Re: An alternative to gdk-pixbuf

On Sat, 15 Sep 2018 09:47:33 +0100 John Emmas wrote: > Sorry, I haven't been following this conversation but as a > side-issue... I only noticed this morning that gdk-pixbuf doesn't > seem to be able to load TIF images any more. I've attached a small > file that won't load but I haven't managed

Re: An alternative to gdk-pixbuf

Sorry, I haven't been following this conversation but as a side-issue... I only noticed this morning that gdk-pixbuf doesn't seem to be able to load TIF images any more. I've attached a small file that won't load but I haven't managed to load any TIF image from the ones I've tested this mornin

Re: An alternative to gdk-pixbuf

On Tue, 11 Sep 2018 13:22:17 +0200 Bastien Nocera wrote: > On Tue, 2018-09-11 at 07:40 +0100, John Cupitt via gtk-devel-list > wrote: > > On Tue, 11 Sep 2018 at 03:11, Magnus Bergman > > wrote: > > > On Tue, 11 Sep 2018 00:07:27 +0200 > > > Bastien Nocera wrote: > > > > No, it really isn't:

Re: An alternative to gdk-pixbuf

On Tue, 2018-09-11 at 07:40 +0100, John Cupitt via gtk-devel-list wrote: > On Tue, 11 Sep 2018 at 03:11, Magnus Bergman > wrote: > > On Tue, 11 Sep 2018 00:07:27 +0200 > > Bastien Nocera wrote: > > > No, it really isn't: > > > https://www.cvedetails.com/vulnerability-list/vendor_id-1749/Imagemag

Re: An alternative to gdk-pixbuf

On Tue, 11 Sep 2018 at 03:11, Magnus Bergman wrote: > On Tue, 11 Sep 2018 00:07:27 +0200 > Bastien Nocera wrote: > > No, it really isn't: > > https://www.cvedetails.com/vulnerability-list/vendor_id-1749/Imagemagick.html > > > > We want to have less CVEs, not more. > > I see what you mean. A few o

Re: An alternative to gdk-pixbuf

On Tue, 11 Sep 2018 00:07:27 +0200 Bastien Nocera wrote: > On Mon, 2018-09-10 at 22:29 +0200, Magnus Bergman wrote: > > On Mon, 10 Sep 2018 11:31:42 +0200 > > Bastien Nocera wrote: > > > > I do use a library (or two). I've written one plugin that uses > > giflib and one that uses ImageMagick.

Re: An alternative to gdk-pixbuf

On Mon, 2018-09-10 at 22:29 +0200, Magnus Bergman wrote: > On Mon, 10 Sep 2018 11:31:42 +0200 > Bastien Nocera wrote: > > > > I've written loader for GIF that simply wraps abydos. In lines of > > > code it's about a quarter the size of the current loader, even > > > including > > > the GIF plugin

Re: An alternative to gdk-pixbuf

On Mon, 10 Sep 2018 07:02:23 + Debarshi Ray wrote: > On Sun, Sep 09, 2018 at 02:57:30AM +0200, Magnus Bergman wrote: > > Many fields of science deal with images of multi > > gigabyte sizes. Ideally any image viewer should be able to handle > > these too with the right plugin (probably using G

Re: An alternative to gdk-pixbuf

On Mon, 10 Sep 2018 11:31:42 +0200 Bastien Nocera wrote: > > I've written loader for GIF that simply wraps abydos. In lines of > > code it's about a quarter the size of the current loader, even > > including > > the GIF plugin for abydos. It might even be slightly smaller with > > the whole of ab

Re: An alternative to gdk-pixbuf

On Sun, 2018-09-09 at 01:23 +0200, Magnus Bergman wrote: > On Fri, 07 Sep 2018 12:51:32 +0200 > Bastien Nocera wrote: > > > > > Gegl is great for image editing. But not as much for simple > > > > viewing. > > > > > > This is debatable. If I'm viewing a 4000x4000 RGB image on a > > > hidpi > >

Re: An alternative to gdk-pixbuf

On Mon, Sep 10, 2018 at 09:40:13AM +0100, jcup...@gmail.com wrote: > I make a gtk viewer that can display large images efficiently (over > 100,000 x 100,000), linked above. I hit a few other issues: > > 1. You can't use a large ScrolledWindow and only paint the visible > area, since you can easily

Re: An alternative to gdk-pixbuf

On Mon, 10 Sep 2018 at 08:02, Debarshi Ray wrote: > > too with the right plugin (probably using GEGL in that case). But I > > think the problem with large images (say 12000x12000 or so) is giving > > it to the application as a pixmap. From my own tests it seams it's fine > > at least as long as th

Re: An alternative to gdk-pixbuf

On Sun, Sep 09, 2018 at 02:57:30AM +0200, Magnus Bergman wrote: > Many fields of science deal with images of multi > gigabyte sizes. Ideally any image viewer should be able to handle these > too with the right plugin (probably using GEGL in that case). But I > think the problem with large images (s

Re: An alternative to gdk-pixbuf

On Fri, 7 Sep 2018 17:28:04 + Debarshi Ray wrote: > Hey Magnus, > > I haven't yet worked my way through the whole thread. It's pretty > long and will take me a while longer, but I did want to mention a > few things before the weekend draws me away from the computer. > > On Wed, Sep 05, 2018

Re: An alternative to gdk-pixbuf

On Fri, 07 Sep 2018 12:51:32 +0200 Bastien Nocera wrote: > > > Gegl is great for image editing. But not as much for simple > > > viewing. > > > > This is debatable. If I'm viewing a 4000x4000 RGB image on a hidpi > > display I'm already pushing gdk-pixbuf and cairo to their limits > > because

Re: An alternative to gdk-pixbuf

On Thu, 06 Sep 2018 13:03:03 -0500 Federico Mena Quintero wrote: > On Wed, 2018-09-05 at 17:28 +0100, Emmanuele Bassi via gtk-devel-list > wrote: > > > In the near future, I'll very likely deprecate most of GdkPixbuf's > > API, except for the I/O operations; I'd also be happy to seal off > > mos

Re: An alternative to gdk-pixbuf

On Wed, Sep 05, 2018 at 08:25:05PM +0200, Magnus Bergman wrote: > Gegl is great for image editing. But not as much for simple viewing. It > doesn't do animation People have been creating and playing videos with it: http://gegl.org/gcut.html > Also it only loads images from the > file system and i

Re: An alternative to gdk-pixbuf

Hey Magnus, I haven't yet worked my way through the whole thread. It's pretty long and will take me a while longer, but I did want to mention a few things before the weekend draws me away from the computer. On Wed, Sep 05, 2018 at 12:02:45AM +0200, Magnus Bergman wrote: > Over the years it has be

Re: An alternative to gdk-pixbuf

On Thu, 2018-09-06 at 11:39 +0100, Emmanuele Bassi via gtk-devel-list wrote: > On Wed, 5 Sep 2018 at 19:25, Magnus Bergman < > magnus.berg...@snisurset.net> wrote: > > On Wed, 5 Sep 2018 17:28:22 +0100 > > Emmanuele Bassi wrote: > > > > > We're phasing out Cairo in favour of the CSS rendering mod

Re: An alternative to gdk-pixbuf

On Thu, 6 Sep 2018 11:39:59 +0100 Emmanuele Bassi wrote: > On Wed, 5 Sep 2018 at 19:25, Magnus Bergman > wrote: > > > On Wed, 5 Sep 2018 17:28:22 +0100 > > Emmanuele Bassi wrote: > > > > > We're phasing out Cairo in favour of the CSS rendering model, > > > implemented on top of OpenGL and Vu

Re: An alternative to gdk-pixbuf

On Wed, 2018-09-05 at 17:28 +0100, Emmanuele Bassi via gtk-devel-list wrote: > In the near future, I'll very likely deprecate most of GdkPixbuf's > API, except for the I/O operations; I'd also be happy to seal off > most of its internals, within the ABI stability promise, to avoid > leakage of int

Re: Problems with git.gnome.org

Are you trying to access a repository using a `git://` URL? That has been deprecated a long time ago, for security reasons, and with GitLab it was removed altogether. Ciao, Emmanuele. On Thu, 6 Sep 2018 at 14:09, John Emmas wrote: > Hi guys - sorry for posting this here but I've tried gnome's

Re: Problems with git.gnome.org

On Thu, 2018-09-06 at 15:30 +0100, John Emmas wrote: > On 06/09/2018 14:11, Bastien Nocera wrote: > > > > It's gitlab.gnome.org, not git.gnome.org anymore. > > > > Thanks Bastien - but that doesn't seem to help... :-( > > I see exactly the same error except that whereas it previously said > "f

Re: Problems with git.gnome.org

On 06/09/2018 14:11, Bastien Nocera wrote: It's gitlab.gnome.org, not git.gnome.org anymore. Thanks Bastien - but that doesn't seem to help... :-( I see exactly the same error except that whereas it previously said "fatal: unable to connect to git.gnome.org" it now tells me:- "fatal: unabl

Re: Problems with git.gnome.org

On Thu, 2018-09-06 at 14:09 +0100, John Emmas wrote: > Hi guys - sorry for posting this here but I've tried gnome's > 'gitlab-issues' mailing list and couldn't get any response. Maybe > someone here can help..? > > For the past few weeks I've been seeing errors if I try to update > (i.e. > pul

Re: An alternative to gdk-pixbuf

On Thu, 6 Sep 2018 at 11:40, Emmanuele Bassi via gtk-devel-list wrote: > On Wed, 5 Sep 2018 at 19:25, Magnus Bergman > wrote: >> Gegl is great for image editing. But not as much for simple viewing. > > This is debatable. If I'm viewing a 4000x4000 RGB image on a hidpi display > I'm already push

Re: An alternative to gdk-pixbuf

On Wed, 5 Sep 2018 at 19:25, Magnus Bergman wrote: > On Wed, 5 Sep 2018 17:28:22 +0100 > Emmanuele Bassi wrote: > > > We're phasing out Cairo in favour of the CSS rendering model, > > implemented on top of OpenGL and Vulkan, as it's the API that most > > closely matches the requirements of GTK.

Re: An alternative to gdk-pixbuf

On 09/05/2018 06:57 PM, Nicolas Dufresne wrote: > I've replied to a comment about sandboxing image loading to prevent > possible crash buffer overflow from happening. You are now focusing on > an optimization. I believe you should start a new thread. It's relevant because it is the same as the bub

Re: An alternative to gdk-pixbuf

Le mercredi 05 septembre 2018 à 18:43 -0700, Christian Hergert a écrit : > On 09/05/2018 06:18 PM, Nicolas Dufresne wrote: > > Is there any benchmark that would justify this added complexity ? Also, > > there will be more context switch, so cache misses will take more time > > then just loading the

Re: An alternative to gdk-pixbuf

On 09/05/2018 06:18 PM, Nicolas Dufresne wrote: > Is there any benchmark that would justify this added complexity ? Also, > there will be more context switch, so cache misses will take more time > then just loading the icon directly. Just because you've decoded into a non-shareable page of memory

  1   2   3   4   5   6   7   8   9   10   >