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 1f3L78-0006Vu-7P for pgadmin-hackers@arkaria.postgresql.org; Tue, 03 Apr 2018 12:32:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f3L77-0006iD-4O for pgadmin-hackers@arkaria.postgresql.org; Tue, 03 Apr 2018 12:32:37 +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 1f3L76-0006i3-VL for pgadmin-hackers@lists.postgresql.org; Tue, 03 Apr 2018 12:32:37 +0000 Received: from mail-wm0-x243.google.com ([2a00:1450:400c:c09::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f3L72-0006Gs-CY for pgadmin-hackers@postgresql.org; Tue, 03 Apr 2018 12:32:36 +0000 Received: by mail-wm0-x243.google.com with SMTP id v21so33477870wmc.1 for ; Tue, 03 Apr 2018 05:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hcynTsSMdbPoLU5cjrRvkCZ5ixwdf9jsPCKjILAQR0k=; b=f9+XEmuNGVjaQ3lMxKb0leBbympvoOBhFy0arsojFa2lpzb117Wx1UXS9OREGgF+QB lD2gFp0QelsXKjKRIb11h0/aDdOlusahshhYZf0Usrkv+8r44JoqubXtBvavKnodVi2F 9gE3A2PvGTukJ5JZCmuSrheS1e7l4zCYTXtTCZkVG2Af0dwnaJqsnp86WcuKujEdcdby UK/ybscwPL4t/UELtTeqWtjT6sG/zfpIR2hSFwLZsE+sSs65Jw+jF0p2SAYJZbqMskrq 4uZh2sUQ48yklOT9VH/khDHKCueqLn3FooKCRmfzhwEe3PVwcDkfJ3zS/x2X3dc/VQVJ aXjw== 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=hcynTsSMdbPoLU5cjrRvkCZ5ixwdf9jsPCKjILAQR0k=; b=TP+8zl5yLXe5St4oI87b2c3g2TvuNr2JlXBwB6Iq83CHnLd55JWrvMc6toqqGgngyt xvZi69xh4KFmz80/6mltD8nqk5OjMewCaNhZ+Gytor0tC0t/H3P4wucRfchSqyUXTp8d o+/LnlrUjkYKuTxseKAcY0xlYldDb9GIyKbBwVmJWfvbscHL/DdETKgVa7OQqIQTlZ0d DbBuD0acy6J2SQF8ECeju3Z1sSj/xYoVitO+hnfEWnscF7w+L078DL3wtwUXNBM7C8nv k8SjSa/cdCH12wTaUYUy2AWCt+5gG8HFgDBF2DzXQChEB0qNUs6yLRJsWqQVsFfsN7K4 G/FQ== X-Gm-Message-State: AElRT7GxnMmGvI3rUnDBmfqYfcjk46uG1UR0Wq128u2H97QmAx5A1n6C duDeer5ZzKLSPZ5kSUMlrF5q4gp9B0Y+T+iVxSAD3Q== X-Google-Smtp-Source: AIpwx4/Z8JrD9jrCkDbN8IvKQF1tBByevkCpD15PuCeGoFsoPRSMKg2W+fogMWX7QPCpxY/pV+uFogPgx3+yXxCe3N8= X-Received: by 10.28.91.65 with SMTP id p62mr4551399wmb.140.1522758750584; Tue, 03 Apr 2018 05:32:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.69.220 with HTTP; Tue, 3 Apr 2018 05:32:30 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Tue, 3 Apr 2018 13:32:30 +0100 Message-ID: Subject: Re: pgAdmin4 - Issue of unmaintained libraries To: Murtuza Zabuawala Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="001a1144161a685a130568f0e66f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a1144161a685a130568f0e66f Content-Type: text/plain; charset="UTF-8" Hi On Tue, Apr 3, 2018 at 1:22 PM, Murtuza Zabuawala < murtuza.zabuawala@enterprisedb.com> wrote: > Hi Team, > > As we are heavily dependent on 3rd party JS libraries and some of them are > no longer actively maintained by their respective authors (Last commit was > approximate year ago). > > Some of the core libraries which are no longer actively maintained are, > - Backbone > - wcDocker > - aciTree > - Backgrid /Backform > - jQuery 1.x > version > > What would be our future plans when it comes to fixing the issues in the > core libraries or adding new feature? > (Ref: Email thread > > ) > Well jQuery can be updated can't it? wcDocker is, as far as I'm aware, the only library of it's kind. Unless something else has surpassed it in the last couple of years, there's nothing even close in functionality to it. aciTree was in a similar position, though Joao and team think there may be other candidates now. As for Backbone/Backgrid/Backform, I don't know. Backbone could maybe be replaced with React eventually. Not sure about the others. In any case, this is likely to be a problem on an ongoing basis - and I think we need to consider the future on a case by case basis when necessary. It may mean moving to a different library, or it may mean forking components, or it may be the upstream may have not had any commits for a long time simply because there is no development happening right now, but bugs may still be fixed. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a1144161a685a130568f0e66f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Tue, Apr 3, 2018 at 1:22 PM, Murtuza Zabuawala &= lt;= murtuza.zabuawala@enterprisedb.com> wrote:
Hi Team,

As we are heavily dependent on 3rd party JS l= ibraries and some of them are no longer actively maintained by their respec= tive authors (Last commit was approximate year ago).

Some of the core li= braries which are no longer actively maintained are,
- wcDocker
- Backgrid/Backform
- jQuery 1.x version

What wo= uld be our future plans when it comes to fixing the issues in the core libr= aries or adding new feature?
(Ref:=C2= =A0Email thread)
<= br>
Well jQuery can be updated can't it?

=
wcDocker is, as far as I'm aware, the only library of it's kin= d. Unless something else has surpassed it in the last couple of years, ther= e's nothing even close in functionality to it. aciTree was in a similar= position, though Joao and team think there may be other candidates now.

As for Backbone/Backgrid/Backform, I don't know.= Backbone could maybe be replaced with React eventually. Not sure about the= others.

In any case, this is likely to be a probl= em on an ongoing basis - and I think we need to consider the future on a ca= se by case basis when necessary. It may mean moving to a different library,= or it may mean forking components, or it may be the upstream may have not = had any commits for a long time simply because there is no development happ= ening right now, but bugs may still be fixed.=C2=A0

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

EnterpriseDB= UK: http://www.e= nterprisedb.com
The Enterprise PostgreSQL Company
--001a1144161a685a130568f0e66f--