Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tgl88-00DMry-8w for pgadmin-hackers@arkaria.postgresql.org; Sat, 08 Feb 2025 13:44:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tgl76-0081yJ-Dp for pgadmin-hackers@arkaria.postgresql.org; Sat, 08 Feb 2025 13:43:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tgl76-0081yA-2j for pgadmin-hackers@lists.postgresql.org; Sat, 08 Feb 2025 13:43:16 +0000 Received: from mail-il1-x12f.google.com ([2607:f8b0:4864:20::12f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tgl72-003wuO-1s for pgadmin-hackers@postgresql.org; Sat, 08 Feb 2025 13:43:14 +0000 Received: by mail-il1-x12f.google.com with SMTP id e9e14a558f8ab-3cf880d90bdso9159955ab.3 for ; Sat, 08 Feb 2025 05:43:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1739022192; x=1739626992; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cZvR9BZqnkdhAZyzHpMxKu8QhBC/d9iq3Kd9LSibie8=; b=lH949N2O5YLprt151cQ0ckOcS6PhjuabSfWz9V5kQyzGjfRsV+GekZh8xOSnowfTz6 6D3EJ9SnLUbG63ULXq6YQT8KtC3mm+E5oWhiFXmMlOoRKAAs/uni5TO/dNAezYqoj8d8 l6PwQkTFrht7hzefDonrDDC97/ZPJvjmwxWcOsTP9DbZ7dBiL4x/5/bf35L2l+MEIk0g 2H9dyu+H65ECwgwdtldyBOrvI7h4yPP4EtHJUeYtJ408To2YBLPMLl/eptMfn53BTfcE zpJp/qxFG0v1IL4eBXUSb5jbLvuwHS+2aaLspjXDynIX4YNdRksKCAFJsGkQ+EA14mHl 2Oog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739022192; x=1739626992; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=cZvR9BZqnkdhAZyzHpMxKu8QhBC/d9iq3Kd9LSibie8=; b=fz42+g8goHijD+Nyx2jo8x7eBu1Dw448rHn5PLl3j5lU0qRkgaQzFI4qCdGZWieSB6 l3ZQseYAZMMxihPFHhruHUEpZqxmxjL+GvQW4+M5dDGDRruqcAx8SH3YH0CVqvAVLzd3 VFng15PuBtSFW82IDozJKmbH70zDEW7tnWgViwPOyO5PxZN8kHWvHo8wUTWQZX7Vg42O NtpXY4kGMjPT4w0Qt4Ma5QGPIO4cfdZ20IsXTlk3HRBajxiNST4Q0T0jCeXmplVvh8j4 Pc9cWF3u9NHvx4bZNmVYyWA/NRsF0kxlQoq4Wqu4IafTJsXr6rxtpW2advWsqCSLyEMy f3WQ== X-Gm-Message-State: AOJu0YyyGNCEADMvTdnEHj9Q8iKIgEjNRpRfuqbjNDvN6R5qy7Ute8hQ 6bjqHEwB+M5uZ+k/fQ4UEif+Qv4MQ1mr1arwwr/Q2pKPhqTYY+B+LBf+0Bx705gSEXsprwMUkz/ oMbZcowYxUMVc9mwUJiVsiJsDvrKtUgqO8/vW X-Gm-Gg: ASbGncvo73ATXlQbXvtbfaemxg7JGBb3EOOzPA1o7dRGKj7mtR7tmzoRbfQk4aBHriy UJEgM7vvdg9IMPT3Kt5a2oTs0er/4kqJmZxXi8sEbetXvHbh0bI/e5uniMF8R6Y8MKE33oodUyM 4= X-Google-Smtp-Source: AGHT+IGHUCtBytmHMSRcFHXbcmMvTXVlozkBB0v6WDHJIFn7HVSIpMEDNpt3qTM3z9olpS9xdoigqshTdVyHz+RxtOc= X-Received: by 2002:a05:6e02:b26:b0:3ce:9149:a8b1 with SMTP id e9e14a558f8ab-3d13dd6747amr46660985ab.9.1739022191948; Sat, 08 Feb 2025 05:43:11 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Murtuza Zabuawala Date: Sat, 8 Feb 2025 19:13:00 +0530 X-Gm-Features: AWEUYZldSWh-9oLUDRISegLedo8aenvrWj3cgKjpz17WIAojPISeETMM8gFi1Do Message-ID: Subject: Re: The new workspace layout To: Anthony DeBarros Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000021817062da1a8f1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000021817062da1a8f1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +1 On Fri, 7 Feb, 2025, 17:38 Anthony DeBarros, wrote: > Dear Hackers, > > I have great respect for your efforts to continuously develop pgAdmin 4, > and it has certainly come a long way since version 1.0. Not to mention, > it=E2=80=99s free. Thank you for all your hard work. > > All that said, I think making the new Workspace layout the default in v > 9.0 was a regression and not an improvement, and already I see issues[1] > raised[2] from users. > > I use pgAdmin and DataGrip every day for writing queries, and I have a > fundamental issue with the new layout. Having the object explorer in a pa= ne > to the left of the query editor is a standard setup, and rightly so =E2= =80=94 it=E2=80=99s > hard to remember names of tables and columns, and drag-and-drop makes lif= e > easier. Having a layout that requires me to click another pane and > disappear the query itself, then click back, is too many steps. > Autocomplete doesn=E2=80=99t fill the need. > > Yes, I understand I can switch to =E2=80=9CClassic,=E2=80=9D and I=E2=80= =99ve done so. But I want > to be an advocate for newer users and others who are upgrading and won=E2= =80=99t > really understand what=E2=80=99s going on, where in settings to change th= e layout, > etc. > > A more gentle user experience for this type of change would have been to > have v 9.0 keep the =E2=80=9CClassic=E2=80=9D layout as the default and a= lert users upon > first launch that a new workspace layout was available =E2=80=94 and expl= ain where > in the settings to make the change. Small popups announcing new features > are a standard UX feature these days. > > That way, people can move on from the familiar to the new and know that > they can switch back if they=E2=80=99d like. Trust me when I tell you tha= t many, > many pgAdmin users are students and people new to SQL who need hand-holdi= ng > from time to time. > > Thanks for listening, > Anthony > > [1] > https://github.com/pgadmin-org/pgadmin4/issues/7708#issuecomment-26402964= 46 > [2] https://github.com/pgadmin-org/pgadmin4/issues/8426 > > > --000000000000021817062da1a8f1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
+1

On Fri, 7 Feb, 2025, 17:38 Anthon= y DeBarros, <anthonymdebar= ros@gmail.com> wrote:
<= div dir=3D"ltr">Dear Hackers,

I have great r= espect for your efforts to continuously develop pgAdmin 4, and it has certa= inly come a long way since version 1.0. Not to mention, it=E2=80=99s free.= =C2=A0 Thank you for all your hard work.

All that said, I think making the new Workspace layout the d= efault in v 9.0 was a regression and not an improvement, and already I see = issues[1] raised[2] from users.

I use pgAdmin and DataGrip every day for writing queries, and I have = a fundamental issue with the new layout. Having the object explorer in a pa= ne to the left of the query editor is a standard setup, and rightly so =E2= =80=94 it=E2=80=99s hard to remember names of tables and columns, and drag-= and-drop makes life easier. Having a layout that requires me to click anoth= er pane and disappear the query itself, then click back, is too many steps.= Autocomplete doesn=E2=80=99t fill the need.

Yes, I understand I can switch to =E2=80=9CClassic,=E2= =80=9D and I=E2=80=99ve done so. But I want to be an advocate for newer use= rs and others who are upgrading and won=E2=80=99t really understand what=E2= =80=99s going on, where in settings to change the layout, etc.

A more gentle user experience for this= type of change would have been to have v 9.0 keep the =E2=80=9CClassic=E2= =80=9D layout as the default and alert users upon first launch that a new w= orkspace layout was available =E2=80=94 and explain where in the settings t= o make the change. Small popups announcing new features are a standard UX f= eature these days.

That wa= y, people can move on from the familiar to the new and know that they can s= witch back if they=E2=80=99d like. Trust me when I tell you that many, many= pgAdmin users are students and people new to SQL who need hand-holding fro= m time to time.

Thanks for= listening,
Anthony

<= div dir=3D"ltr">[1]=C2=A0= https://github.com/pgadmin-org/pgadmin4/issues/7708#issuecomment-2640296446=

=

--000000000000021817062da1a8f1--