Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eyxJp-0004Ov-Jj for pgadmin-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 10:19:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eyxJo-0008NC-8g for pgadmin-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 10:19:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eyxJo-0008N2-3O for pgadmin-hackers@lists.postgresql.org; Thu, 22 Mar 2018 10:19:36 +0000 Received: from mail-io0-x22a.google.com ([2607:f8b0:4001:c06::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eyxJi-0002eG-QI for pgadmin-hackers@postgresql.org; Thu, 22 Mar 2018 10:19:35 +0000 Received: by mail-io0-x22a.google.com with SMTP id 141so10279736iou.12 for ; Thu, 22 Mar 2018 03:19:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UHqZpliYzb3O6xkkt0klId/+6SWacuY5jtU02etp0LQ=; b=0O4A5PLGOC+VU+elmttYUvP1v0uF3e0rMLZ0EMOCjIqbj0Bm+G407X6rhziMlp60VW 1SD/n8p6Z4yXxYAw7BxTBZRHKGdkc0uN2Mu/ZuOGnSjU/UXVHVlCTSnvi60RxPv3UewR 5YS3neuzDKnB+81xDUU+rDgt69qRtlXX3enAICfoNtTbJc4aMxqUpFkMOiZW0J8sdlcL jeGFstLdsqXXQcZSVdPjbnpaTrh7s8WWYA/G9VmluQ+NNN5yAH1ywh0ZrVH0Gt9d53tt 4ADT/ggBoP4aj+6yvUXTo+wYJ9/tAAwBK2NXJ8T4Zr0Nb7Kgqwimh/q2xVjut2tLhVnp RWpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UHqZpliYzb3O6xkkt0klId/+6SWacuY5jtU02etp0LQ=; b=GGtoJBZX/iL7IuSW2a0pcsvGPh63AVzm9gymMo5YlQFtx47MGy79LB5H3RkvAs5trF CoZlrMkSwnWHM6oD/QfuSKHjMz44W4bUVxu4s0P7dtIkooIhOaB9CQmRe6p2GP/ZRdB/ eaJ3sHu7xguoklqtMc+R6DjwMMjA5aaZkoTNT5WAFBEtQCHTf7w6DNdRRD0O1MnpmnLN gcULXb/dVptjgBa2EMrTDLHGXYowhGWbhGzIQHKPmG5Abl/esikOuKY0T+ZTdBKj8V/V kFvHnNoVdhoM4wYqxhcQ7E0Jtp8GYtP+vP5aoE34e/K/dS20dE9aqrt7RS4H6BZAxUof u/Yg== X-Gm-Message-State: AElRT7HK95ZBvxQeis4Fxj33aAdpQ0qlaIXY8JN8y5ImUkXjDe3TCceX 1NnB+/5feNDFp4OAYqp+wh4preE/kSCa8yqaQZBg0Q== X-Google-Smtp-Source: AG47ELs74RTpAUIGpjbQsNmq50vMojEzTjC3iw4r2sj30lQGmfxprBnc3htSk3PhalMYsa4yuYqWnHtfpBxEdx+kKSk= X-Received: by 10.107.8.36 with SMTP id 36mr23993857ioi.167.1521713968196; Thu, 22 Mar 2018 03:19:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.9.68 with HTTP; Thu, 22 Mar 2018 03:19:27 -0700 (PDT) In-Reply-To: References: From: Neel Patel Date: Thu, 22 Mar 2018 15:49:27 +0530 Message-ID: Subject: Re: Showstopper desktop runtime issue To: Dave Page Cc: pgadmin-hackers , Akshay Joshi , Ashesh Vashi , Joao Pedro De Almeida Pereira , Robert Eckhardt Content-Type: multipart/alternative; boundary="001a113fb8848648c30567fda4a4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a113fb8848648c30567fda4a4 Content-Type: text/plain; charset="UTF-8" Hi, On Thu, Mar 22, 2018 at 3:19 PM, Dave Page wrote: > All, > > As you know, the 3.0 release is currently on hold as we discovered late > yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and > later. This is because the GTK project, and later Gnome, have removed > support for the System Tray on which the new runtime relies. > > They have replaced it with a notification mechanism, however this doesn't > really meet our needs as what we want is a place (the tray icon) to attach > a menu to control the pgAdmin server; we don't really use notifications as > such. > > I see a number of possible ways around this: > > 1) Return to the previous runtime. I think this is at best a short-term > solution, as the re-visited Annulen version of the QtWebKit seems to be > getting little attention at the moment, and this would re-introduce many > known bugs caused by WebKit. > > 2) Re-work the current runtime code to remove the tray icon, and utilise > desktop/start menu items to signal the running instance to show the logs, > configure the server, exit etc. This should work, but will be kinda klunky. > > 3) Put effort into polishing Joao's Electron based runtime. This might be > a good long term solution as it would remove the need to have any C++ code > of our own, and might allow us to use Electron's update mechanism to do > software updates. The downsides are that we would lose support for dockable > tabs (new windows only), and it wouldn't work on CentOS/RHEL 6 which we > currently support. > > Thoughts and comments please folks? How do we want to proceed? I'm > currently leaning towards 2 for v3, and possibly moving to 3 in the long > term. > As per our previous efforts on Qt's web rendering framework, I am not in favor of adding it again as it add lots of dependency and complexity. I would suggest to go for option 2 - To re-work the current runtime code and find out how to get already running instance of pgadmin4. > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --001a113fb8848648c30567fda4a4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Thu, Mar 22, 2018 at 3:19 PM, Dave Page <dpage@pgadmin.org> wrote:
All,
As you know, the 3.0 release is currently on hold as we discov= ered late yesterday that the re-vamped desktop runtime will not run on Gnom= e 3.26 and later. This is because the GTK project, and later Gnome, have re= moved support for the System Tray on which the new runtime relies.=C2=A0

They have replaced it with a notification mechanism,= however this doesn't really meet our needs as what we want is a place = (the tray icon) to attach a menu to control the pgAdmin server; we don'= t really use notifications as such.

I see a number= of possible ways around this:

1) Return to the pr= evious runtime. I think this is at best a short-term solution, as the re-vi= sited Annulen version of the QtWebKit seems to be getting little attention = at the moment, and this would re-introduce many known bugs caused by WebKit= .

2) Re-work the current runtime code to remove th= e tray icon, and utilise desktop/start menu items to signal the running ins= tance to show the logs, configure the server, exit etc. This should work, b= ut will be kinda klunky.

3) Put effort into polish= ing Joao's Electron based runtime. This might be a good long term solut= ion as it would remove the need to have any C++ code of our own, and might = allow us to use Electron's update mechanism to do software updates. The= downsides are that we would lose support for dockable tabs (new windows on= ly), and it wouldn't work on CentOS/RHEL 6 which we currently support.<= /div>

Thoughts and comments please folks? How do we want= to proceed? I'm currently leaning towards 2 for v3, and possibly movin= g to 3 in the long term.

As per = our previous efforts on Qt's web rendering framework, I am not in favor= of adding it again as it add lots of dependency and complexity.=C2=A0
= I would suggest to go for option 2 - To re-work the current runtime code an= d find out how to get already running instance of pgadmin4.

<= /div>


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

Enterp= riseDB UK: http:/= /www.enterprisedb.com
The Enterprise PostgreSQL Company

--001a113fb8848648c30567fda4a4--