MIME-Version: 1.0
From: Dave Page <dpage@pgadmin.org>
Date: Thu, 22 Mar 2018 09:49:27 +0000
Message-ID: 
 <CA+OCxoyjbMa6EK=Wu+d56S7teJ7YRVP2sY73BbYFwiRZAwUetA@mail.gmail.com>
Subject: Showstopper desktop runtime issue
To: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Cc: Akshay Joshi <akshay.joshi@enterprisedb.com>,
 Neel Patel <neel.patel@enterprisedb.com>,
	Ashesh Vashi <ashesh.vashi@enterprisedb.com>,
	Joao Pedro De Almeida Pereira <jdealmeidapereira@pivotal.io>,
 Robert Eckhardt <reckhardt@pivotal.io>
Content-Type: multipart/alternative; boundary="f403045c4e223dafe20567fd39a1"
Precedence: bulk

--f403045c4e223dafe20567fd39a1
Content-Type: text/plain; charset="UTF-8"

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.

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

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

--f403045c4e223dafe20567fd39a1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">All,<div><br></div><div>As you know, the 3.0 release is cu=
rrently 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 proje=
ct, and later Gnome, have removed support for the System Tray on which the =
new runtime relies.=C2=A0</div><div><br></div><div>They have replaced it wi=
th a notification mechanism, however this doesn&#39;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&#39;t really use notifications as such.</div><div><=
br></div><div>I see a number of possible ways around this:</div><div><br></=
div><div>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.</div><div><br></div><div>2) Re-work the curre=
nt runtime code to remove the tray icon, and utilise desktop/start menu ite=
ms to signal the running instance to show the logs, configure the server, e=
xit etc. This should work, but will be kinda klunky.</div><div><br></div><d=
iv>3) Put effort into polishing Joao&#39;s Electron based runtime. This mig=
ht 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&#39;s update mechanism=
 to do software updates. The downsides are that we would lose support for d=
ockable tabs (new windows only), and it wouldn&#39;t work on CentOS/RHEL 6 =
which we currently support.</div><div><br></div><div>Thoughts and comments =
please folks? How do we want to proceed? I&#39;m currently leaning towards =
2 for v3, and possibly moving to 3 in the long term.<br clear=3D"all"><div>=
<br></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail_sig=
nature">Dave Page<br>Blog: <a href=3D"http://pgsnake.blogspot.com" target=
=3D"_blank">http://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<br><br>Ent=
erpriseDB UK: <a href=3D"http://www.enterprisedb.com" target=3D"_blank">htt=
p://www.enterprisedb.com</a><br>The Enterprise PostgreSQL Company<br></div>
</div></div>

--f403045c4e223dafe20567fd39a1--