Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2e7g-00056l-L3 for pgadmin-support@arkaria.postgresql.org; Thu, 21 Jan 2021 17:51:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2e7f-00029n-It for pgadmin-support@arkaria.postgresql.org; Thu, 21 Jan 2021 17:51:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2cOt-0004B3-98; Thu, 21 Jan 2021 16:01:35 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l2cOm-0001DD-7v; Thu, 21 Jan 2021 16:01:34 +0000 Received: by mail-lf1-x12c.google.com with SMTP id o10so3179766lfl.13; Thu, 21 Jan 2021 08:01:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kKzrvVBfb8nvA7uQ3+VpZsjg/JEBL6hGmrXrq1Nbu9k=; b=VZPXn8Q/vUp8mi49+eBcOH2lucgpg7sEWgx/FfXmry9f7McsOGArxOrSDEtTbi+8HS /uRSg5xcTYhCr0JAQoiGh1vX7FV1WV3KH9TNwLUi2fvALe3NJj0sXlUL3RxCGdRbD0ZT uEnLMZkZwnspSetZmBDGvplLR+Vi4sd37iswcrDH/r8sT8Nb60QPuIRXGk0elCQRIdLP DGbuQySFe/yCuDGNRZJvkz1M5p3rDZQcJaw/QvMykZxjStHJHKmg90vWOFACpru/wQ4p LVxisqjji0ZDYoRb3gh3GL4msmZSOuRf3iZtZU1j9W76EywMQ5XrxjvQwaPd2GWFLJ2i +FKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kKzrvVBfb8nvA7uQ3+VpZsjg/JEBL6hGmrXrq1Nbu9k=; b=jwPghRSG/nugpyxX0euZXRHzpBr10CDsXCXU5PGBBrM/+FIrjxdmY5203hFwWQD/uj tQVJXkVqw7+KUZrlORjX2Kmj2BLwdNLj5iZPEtclzwCiztDHV4qOAegHUpUCDMA5tdwR a/Gh4OlNZfMNLzGLON1f73GGs/Q8ObI+PrtZ72X4xuFg2xjDTN7DUow5ohI0fOGjkJjK VIhzdXJ10MM+iXUIKKL4wWw22c4Cae4nZVL3DtZBZrmUVhWmt7RlDqZCS34gJ2w6J0Cr cjy8rcEX1qWpcMmxQkXWlhBjedZ267mn7rez3rWjYi+IttVR/HGYOH2/NTEWrzMujZfH OvGg== X-Gm-Message-State: AOAM532bWVSvbOF3HMotU1EF7ntt5I0hL8NFnpavExQrqMOTLSKoY727 hSggwxWXvRbLpkn2TICDeF7RYVCiljHWXWEVfEQry+PuL0o= X-Google-Smtp-Source: ABdhPJyvnfJHZvWQO2iCDIDDrbtfScliC0rqUjhIIrddrsXC0O+7Tj349l2ywPfqMG8XWit1VPPaNtfPY9DXp488j08= X-Received: by 2002:ac2:5442:: with SMTP id d2mr7035707lfn.154.1611244885722; Thu, 21 Jan 2021 08:01:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: richard coleman Date: Thu, 21 Jan 2021 11:01:14 -0500 Message-ID: Subject: Re: Testing required: pgAdmin 4 with new desktop runtime To: Dave Page Cc: pgadmin-hackers , pgAdmin Support Content-Type: multipart/alternative; boundary="0000000000000f4d7c05b96b2fc7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000000f4d7c05b96b2fc7 Content-Type: text/plain; charset="UTF-8" Dave, Sounds promising, can the new beta be installed alongside the existing version? Thanks, rik. On Thu, Jan 21, 2021 at 10:56 AM Dave Page wrote: > All, > > As you know, when run in Desktop mode, pgAdmin 4 uses a server process > which runs all the time and opens a browser window to display the UI. Very > early versions used a Qt based runtime that integrated the browser and > server which gave a much more "normal" application feel, but unfortunately > we found that the Qt browser components had performance issues. > > We've been working on a new runtime (based on NWjs, similar to Electron) > to allow us to get rid of the separate server process, and I'm please to > offer builds for testing at: > > https://developer.pgadmin.org/builds/nwjs-2021-01-21-1/ > > There you'll find an installer for 64 bit Windows, a DMG for macOS, and > RPM and DEB packages for Fedora 31, 32 & 33, RHEL/CentOS 7 & 8, Debian 9, > 10 & 11 and Ubuntu 18.04, 20.04 and 20.10. > > These builds are based on development code currently in git that will be > released as v4.30 next week. This includes phase 1 of our Kerberos support > (for logging into pgAdmin, but *not* the database servers), and the new ERD > tool. This code is still going through QA and final improvement, so please > bear that in mind. > > We're aiming to release v5.0 of pgAdmin 4 in late February, based on the > new runtime, so would appreciate as much help and feedback as we can get > prior to the release. > > Whilst I'm writing, I'd also like to give an update on platform support > changes; > > - As previously noted in release announcements, Windows 32 bit builds are > deprecated. v4.29 will be the last 32 bit Windows build supported. > > - Canonical have dropped support for Ubuntu 19.10, and now removed all of > the packages repositories. We have therefore had to drop support for it as > well; the last supported version of pgAdmin on Ubuntu 19.10 will be v4.29. > > - Due to the age of the Python version it ships with, we've had to stop > producing builds for Ubuntu 16.04 (some of the security related Python > modules are no longer supported on older Python versions). v4.30 will be > the last version supported on Ubuntu 16.04. > > - Builds for Ubuntu 20.10 and Debian 11 (Bullseye/testing) have been added > for the v4.30 release onwards. > > Thank you! > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EDB: http://www.enterprisedb.com > > --0000000000000f4d7c05b96b2fc7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dave,=C2=A0

Sounds promising, can the n= ew beta be installed alongside=C2=A0the existing version?

Thanks,=C2=A0

rik.

On Thu, Jan 21, 20= 21 at 10:56 AM Dave Page <dpage@pga= dmin.org> wrote:
All,

As you know, when run in D= esktop mode, pgAdmin 4 uses a server process which runs all the time and op= ens a browser window to display the UI. Very early versions used a Qt based= runtime that integrated the browser and server which gave a much more &quo= t;normal" application feel, but unfortunately we found that the Qt bro= wser components had performance issues.

We've = been working on a new runtime (based on NWjs, similar to Electron) to allow= us to get rid of the separate server process, and I'm please to offer = builds for testing at:


There = you'll find an installer for 64 bit Windows, a DMG for macOS, and RPM a= nd DEB packages for Fedora 31, 32 & 33, RHEL/CentOS 7 & 8, Debian 9= , 10 & 11 and Ubuntu 18.04, 20.04 and 20.10.

T= hese builds are based on development code currently in git that will be rel= eased as v4.30 next week. This includes phase 1 of our Kerberos support (fo= r logging into pgAdmin, but *not* the database servers), and the new ERD to= ol. This code is still going through QA and final improvement, so please be= ar that in mind.

We're aiming to release v5.0 = of pgAdmin 4 in late February, based on the new runtime, so would appreciat= e as much help and feedback as we can get prior to the release.

Whilst I'm writing, I'd also like to give= an update on platform support changes;

- As previ= ously noted in release announcements, Windows 32 bit builds are deprecated.= v4.29 will be the last 32 bit Windows build supported.

- Canonical have dropped support for Ubuntu 19.10, and now removed al= l of the packages repositories. We have therefore had to drop support for i= t as well; the last supported version of pgAdmin on Ubuntu 19.10 will be v4= .29.

- Due to the age of the Python version it= ships with, we've had to stop producing builds for Ubuntu 16.04 (some = of the security related Python modules are no longer supported on older Pyt= hon versions). v4.30 will be the last version supported on Ubuntu 16.04.

- Builds for Ubuntu 20.10 and Debian 11 (Bullseye/te= sting) have been added for the v4.30 release onwards.

<= div>Thank you!

--
--0000000000000f4d7c05b96b2fc7--