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 1thpPS-007KGe-CM for pgadmin-hackers@arkaria.postgresql.org; Tue, 11 Feb 2025 12:30:38 +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 1thpPR-00AIXj-3o for pgadmin-hackers@arkaria.postgresql.org; Tue, 11 Feb 2025 12:30:37 +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 1thpPQ-00AIVj-OK for pgadmin-hackers@lists.postgresql.org; Tue, 11 Feb 2025 12:30:36 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thpPO-000D0C-1W for pgadmin-hackers@postgresql.org; Tue, 11 Feb 2025 12:30:35 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-308e3bd8286so28185421fa.1 for ; Tue, 11 Feb 2025 04:30:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1739277031; x=1739881831; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=WtWthLubPwKL+fUxoBO+UUaTRld1xi924Ne6wSi+JOs=; b=Bcrcsg4aTctf2QjPj5CLoXsZHLegXHnTEEmsXUazTr/p2ZJpjENUFw4O4vOsxGW5xU 6QLxtYT3gsmT5DA7yAts9B+C/kIjmC6U90VroYGxT6f2BvB2gnbHu8pfAkIXDC7pKgYh YSoyFzQ1GpRDmzrTa+TGOA+JaaRcP9xCEl0U6kEmmWSeBedD29vvlWE4yWFiWRjppZ9Q A9DPNIG/LEIYdUzqrwYPby3r/0p8FlWC2B5bnVJ3XVu6vYDw0CZTWW7uOuIYImMHqxvQ ANpQ/llmclupRXyzw68u5Pz6SQAi0DHEMQ3btKkc/BTKiFDUVNUoP115bhC7k/7nWfO0 AaDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739277031; x=1739881831; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=WtWthLubPwKL+fUxoBO+UUaTRld1xi924Ne6wSi+JOs=; b=i4jlIXsMf2UuDP398/tOHr/oJvXJo1K4mD7aSRMtoeT19YS13rYAsgYmg9EdheM1G7 jFGEvDQD9f9C5q8A6lQbseF45lQMV3QkcTeBGS6M5hbfeGUixM2J08LX03QCJesJFNXi tnPOFfJsOLPeUSYxZ+DKiMsZwpmMpOISPdQNns47apYIyvsXIPdWJd1tIVCdp2DqK6FH Rlca6+cz/KqkzDfzmpH55OlfF811EEgKdXx9gBbktxOoqqAeuMV3uFt/iDEaWVB1aWYe UbMaqIJA4VvDwXbHxeBQfYe2Xlg8kDQXQhdsFNWasJ1Hk8Clb4hO/yB1GbJhOhj4URyv CQkw== X-Gm-Message-State: AOJu0YxxYTe0yVY/xllT9sXs1QuG2wLMB7i2noeYMewPNl7UccMd5o/Y 73cNf7281FGMe/hsAibJOO1pEyG40CdNYr1kAIR3zwQ5sJX3hxHgWDCBxX/yTOI8K3+kLA8YACp USc5t65Xh8cfh+UNfPmJGsl1Hnl9kfKsJH9rkpBFPWiqvvr2mcA== X-Gm-Gg: ASbGncv8nrXvpsZpCJ9uY6+HK5WVQpwDRfjIHelFWXoDPmzm2gsI3qZduSxgRbnkVSU qH7SB28/2rpDE/niA/jRpeE96QC/R4RPJZ1jctmvH5ghhUiVpC2mQ6V81lHdGt6Nq+LHFSaT03b huIk0PkuJwWV2LKdI9hylJoJKqG9IY X-Google-Smtp-Source: AGHT+IEuY5Y9NABfD65ui6qqqwpiwH29XreiAU8scMSDwZftAF8d3pLvNWLRupVAohc00latSOw+AseY9c1oSlseUEc= X-Received: by 2002:a05:651c:b0c:b0:308:fedf:8c26 with SMTP id 38308e7fff4ca-308fedf91d1mr4445051fa.7.1739277030863; Tue, 11 Feb 2025 04:30:30 -0800 (PST) MIME-Version: 1.0 From: Akshay Joshi Date: Tue, 11 Feb 2025 18:00:19 +0530 X-Gm-Features: AWEUYZmvnu7J59fqdsyr5BDL2o3mazLMgssKn4zoIdGYHrx5x_Tf2DtQv_RKYT8 Message-ID: Subject: Workspace Layout Update To: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000975d69062ddcfdba" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000975d69062ddcfdba Content-Type: text/plain; charset="UTF-8" Hi All, Based on feedback from some users regarding the new Workspace layout, we've made a few improvements to the logic. With these changes, the *Query Tool* and *PSQL* tabs will now open in the same active workspace where the action is initiated. For example: - If you're currently working in the default workspace with the Tree view and you open the Query Tool/View/Edit Data or PSQL, it will open within the same workspace. - Similarly, if any action is triggered from the *Welcome page* for the Query Tool or PSQL, the respective tab will open in the same active workspace. Additionally, we've introduced a new preference setting: *"Open the Query Tool/PSQL in their respective workspaces"*. By default, this setting is *False*. If set to *True*, it will behave like the v9.0 release, where the Query Tool, PSQL, and Schema Diff tabs will open in their respective workspaces when the Workspace layout is used. We believe this update will provide a more streamlined experience for all users. These changes will be available starting with the v9.1 release scheduled for *March 6th*. However, if you'd like to try them earlier, you can install the nightly build dated 2025-02-12 or above. Akshay Joshi Principle Software Architect enterprisedb.com * Blog*: https://www.enterprisedb.com/akshay-joshi * GitHub*: https://github.com/akshay-joshi * LinkedIn*: https://www.linkedin.com/in/akshay-joshi-086497216 --000000000000975d69062ddcfdba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi All,

Based on feedback from some users re= garding the new Workspace layout, we've made a few improvements to the = logic. With these changes, the Query Tool and PSQL= tabs will now open in the same active workspace where the action = is initiated.

For example:

  • If you're currently working= in the default workspace with the Tree view and you open the Query Tool/Vi= ew/Edit Data or PSQL, it will open within the same workspace.
  • Simil= arly, if any action is triggered from the Welcome page for= the Query Tool or PSQL, the respective tab will open in the same active wo= rkspace.

Additionally, we've introduced a new preference se= tting: "Open the Query Tool/PSQL in their respective workspace= s". By default, this setting is False. If se= t to True, it will behave like the v9.0 release, where the= Query Tool, PSQL, and Schema Diff tabs will open in their respective works= paces when the Workspace layout is used.

We believe this update will = provide a more streamlined experience for all users. These changes will be = available starting with the v9.1 release scheduled for March 6th. However, if you'd like to try them earlier, you can install the= nig= htly build=C2=A0dated=C2=A02025-02-12 or above.=C2=A0

--000000000000975d69062ddcfdba--