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 1eyxln-0006IK-0r for pgadmin-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 10:48:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eyxll-0002Qz-Ud for pgadmin-hackers@arkaria.postgresql.org; Thu, 22 Mar 2018 10:48:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eyxll-0002Pz-Lk for pgadmin-hackers@lists.postgresql.org; Thu, 22 Mar 2018 10:48:29 +0000 Received: from mail-ot0-x232.google.com ([2607:f8b0:4003:c0f::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eyxli-0000ws-Un for pgadmin-hackers@postgresql.org; Thu, 22 Mar 2018 10:48:28 +0000 Received: by mail-ot0-x232.google.com with SMTP id m7-v6so8933992otd.1 for ; Thu, 22 Mar 2018 03:48:26 -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=ilY3hUfYoc7nUQ6kfTAOx4yY8YFnquh5Bj7n//UgT5Q=; b=wR/DfIVVkmW6rVgVwEOwl1mz7RBQ9rcYGcuvI1LTTO90MJq76g+BdWYFmt31x+pNg7 tmeVGF6uMlgyqqgd5JfOf57Glf9jU9HHzrW3d/oaAgPRhTEHGpmVH4N3xmOYYqauaPsM lyDl4Hfq69oJCt75CwhRsuJw8XxOJPhQPJ2i5nJsnw9KjvHHD1drbVBeEii2ywCLh0eP NH9pPlyzgwIF6aypO1vwnz8e2xfsnl37DaotpJNaGj4NIpxF19Ia2riXTQCtKSIGHJD3 cvGqswHdlMdrE25vMWBWsdDZc2FiL/3UTipOe4b7MB1XWvM7Ei8+BlYyzXiv6ehUbJxb PJKg== 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=ilY3hUfYoc7nUQ6kfTAOx4yY8YFnquh5Bj7n//UgT5Q=; b=rSmya4t/Lnx3ZHi7CIDvNdVqwO0TUbcEKbev32t9fME6nP39dbB12kj9PCAa1JMMan ka6vXNPNoJgR2iYRhum2xIDV9zsP7WqoaV+I/0IV53D9EG5Tu6IBlW+fOxIH/bIDqPFr EkpMPuEy1yjx5gUjxwIb9tNx09EhV/nRXpjweXRIy3PNMCqIHOrUbQX5z8f+hbkR60Wn KpyM3zEWVwDsxcMdMiDlTBf7QEtSj+JI6f7J4yLnPHKhptgYq27p/ULV5LES1vS2wUC5 dqiieQeSbcBPb7lktKhM7xHqX1FhZV05ayPo4mSv/GFBabdJpM0+RQUdMzRLOIwA+mMd L46Q== X-Gm-Message-State: AElRT7HYkCV3j+EtDJy27JyxzrGyr9i0NI5MWc8QMJAKPTYA+HaDM9uE tUaHYh4n7QqRssEp4aRe5KN8nOzRDlLA74ZXVZcfkQ== X-Google-Smtp-Source: AG47ELv2HmYXHi+nwyu6S6eEPWsHQ6Rwm4HMmVYfT0z5kH62BiazZQtjj5KMhaDeEMtCrjiVuUWgrCO8nm6RixPLuow= X-Received: by 2002:a9d:2b10:: with SMTP id o16-v6mr8458639otb.155.1521715706149; Thu, 22 Mar 2018 03:48:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.149.198 with HTTP; Thu, 22 Mar 2018 03:48:05 -0700 (PDT) In-Reply-To: References: From: Murtuza Zabuawala Date: Thu, 22 Mar 2018 16:18:05 +0530 Message-ID: Subject: Re: Showstopper desktop runtime issue To: Dave Page Cc: pgadmin-hackers , Akshay Joshi , Neel Patel , Ashesh Vashi , Joao Pedro De Almeida Pereira , Robert Eckhardt Content-Type: multipart/alternative; boundary="0000000000001d55e60567fe0c93" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000001d55e60567fe0c93 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 a= nd > 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 attac= h > a menu to control the pgAdmin server; we don't really use notifications a= s > 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. > =E2=80=8BI would not prefer going back after seeing QtWebkit & QtWebEngine = issues in the past.=E2=80=8B > > 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 klunk= y. > =E2=80=8B+1=E2=80=8B > > 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++ cod= e > 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 dockab= le > tabs (new windows only), and it wouldn't work on CentOS/RHEL 6 which we > currently support. > =E2=80=8BThis is a good alternative but there are some downside of Electron= , - It takes longer to start application - High cpu & ram usage (I have used Slack, Atom & VSCode all of them used Electron) > 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. > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --0000000000001d55e60567fe0c93 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 22, 2018 at 3:19 PM, Dave Page &= lt;dpage@pgadmin.org= > wrote:
= All,

As you know, the 3.0 release is currently on hold a= s 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 Gno= me, have removed support for the System Tray on which the new runtime relie= s.=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 s= ee a number of possible ways around this:

1) Retur= n to the previous runtime. I think this is at best a short-term solution, a= s 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 cause= d by WebKit.
=E2= =80=8BI would not prefer going back after seeing QtWebkit & QtWebEngine= issues in the past.=E2=80=8B
=C2=A0

2) Re-work the c= urrent runtime code to remove the tray icon, and utilise desktop/start menu= items to signal the running instance to show the logs, configure the serve= r, exit etc. This should work, but will be kinda klunky.
=E2=80=8B+1=E2=80=8B
=C2=A0

3) Put effort into polishing Joao's Electron based runt= ime. 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 upd= ate 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 C= entOS/RHEL 6 which we currently support.
=E2=80=8BThis is a good alternative but there are = some downside of Electron,
-= =C2=A0It takes longer to start application
- High cpu & ram usage (I have used Slack, Atom & VSC= ode all of them used Electron)
=


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

= --
Dave Page<= br>Blog: http://p= gsnake.blogspot.com
Twitter: @pgsnake

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

--0000000000001d55e60567fe0c93--