public inbox for [email protected]  

help / color / mirror / Atom feed

From: Murtuza Zabuawala <[email protected]>
To: Dave Page <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Cc: Akshay Joshi <[email protected]>
Cc: Neel Patel <[email protected]>
Cc: Ashesh Vashi <[email protected]>
Cc: Joao Pedro De Almeida Pereira <[email protected]>
Cc: Robert Eckhardt <[email protected]>
Subject: Re: Showstopper desktop runtime issue
Date: Thu, 22 Mar 2018 16:18:05 +0530
Message-ID: <CAKKotZTWLWDHxKf5ct0hUzVbMzjXTg9sxu-0wgTWgthQ2H2FaQ@mail.gmail.com> (raw)
In-Reply-To: <CA+OCxoyjbMa6EK=Wu+d56S7teJ7YRVP2sY73BbYFwiRZAwUetA@mail.gmail.com>
References: <CA+OCxoyjbMa6EK=Wu+d56S7teJ7YRVP2sY73BbYFwiRZAwUetA@mail.gmail.com>

On Thu, Mar 22, 2018 at 3:19 PM, Dave Page <[email protected]> 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.
>
​I would not prefer going back after seeing QtWebkit & QtWebEngine issues
in the past.​


>
> 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.
>
​+1​


>
> 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.
>
​This 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
>

view thread (16+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Showstopper desktop runtime issue
  In-Reply-To: <CAKKotZTWLWDHxKf5ct0hUzVbMzjXTg9sxu-0wgTWgthQ2H2FaQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox