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 1sdNxJ-00F84u-Cj for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Aug 2024 05:50:57 +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 1sdNxH-00DgtE-Ng for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Aug 2024 05:50:55 +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 1sdNxH-00Dgt5-6x for pgadmin-hackers@lists.postgresql.org; Mon, 12 Aug 2024 05:50:55 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdNxD-004Ilu-TE for pgadmin-hackers@postgresql.org; Mon, 12 Aug 2024 05:50:53 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-a7abe5aa9d5so451467566b.1 for ; Sun, 11 Aug 2024 22:50:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1723441850; x=1724046650; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=OxULcp2XL7nrrkVrNIpF/TRzd649CZSys2BhdXImGQo=; b=bEuZz57Hpc3sPGOAL36v8M3pHBOFinpF7y6Vd/k9NJ6aWvvMuXiLym3j/VEc3NJ59X f0mMnxwdhM1LvHVSQ9m48Sdxi1RSjPTxYfEaJ+OOV44mYgPjBNEHTsPl8nUQlB8eHx7X IFpTpD2yDSNgWKZh4WLDWUcUE/jmM/8tYfQWBIdRyo+XuWOgJAxOe9Ducz645j14xER+ HfDollfWGCPi/0U5OmMSpMqTDB/ZKuNwFsGfnvPsGxzTz1wZoOk18+hsirgAoK8R/QEG 3A4z+jww5z1JmTmps9BmOks3kdsSkrR3zSdFHuxLSQy4ldXAp7vqi1EFomlSKid8WpOU J1bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723441850; x=1724046650; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=OxULcp2XL7nrrkVrNIpF/TRzd649CZSys2BhdXImGQo=; b=PUhr4LA0DmckcekKDQqvoIQJd2CZc0CRF+mfiamtP9enwpn7x0ry3w+ZtIyyzmAsQ2 VxWmpS6bUQRzNHZJeFdG+pxCdzGnv14mpCnJhvpPDHhryVLM9GRYn9+GhbPfBWwxO1iq wprTO1X5JU+N67bUSdmLfANv1hYGVq/Z0Z9c6cym79har0bUIJiNdygdmORvMQ2zLY09 u2ZiF6bp/QEPINV5TA4EW4qXxEDTq/tNf2VK+nbTQA0z8i/m2t/yaQq9QKwZGIsGWKpQ 34ii9UvfHikDB4XEmfmMsD0Pd24E+aU1T/4CcJ8c3TUkLLZM3/Cpk6UkxQfv5EcBfqpj dF2w== X-Gm-Message-State: AOJu0YyWtjiXAWy6PuxXSb0AmniUnldanGfXDsJTclEH5ZDhzAt5+zOK Eu75oPpiWf0PnAhTrWaObf8g+5H9Ea7qGXGmbVM7hQYB0SRY3jEE+C0r8RrJjG4sAY0vnxvaIpB yV4iktfIqPykDqAIm/brWVewGNjC0lP3FEEor/z+BOBWoNcz4Lw== X-Google-Smtp-Source: AGHT+IEeE0+D3LyJbi3/eZOKN0mrmVYpX0rDqCe5OdT+GHW2Z8DRSJipsS0mZFbX9w/EqRDySv/OznG+j32UdRbDPh0= X-Received: by 2002:a17:907:80e:b0:a7d:2429:dc16 with SMTP id a640c23a62f3a-a80aa67dad3mr535567166b.65.1723441849847; Sun, 11 Aug 2024 22:50:49 -0700 (PDT) MIME-Version: 1.0 From: Anil Sahoo Date: Mon, 12 Aug 2024 11:20:13 +0530 Message-ID: Subject: Regarding feature #3319 To: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000004076b7061f761324" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004076b7061f761324 Content-Type: text/plain; charset="UTF-8" Hi Hackers, This feature #3319 , demands the Workspace and the Query tool panel to be saved before exiting the application and on restart it will show earlier opened panels. We are already saving the Browser layout, Query tool layout and the Object explorer tree state but to save the contents of panels we will initially start with the Query tool. The below implementation will be done, 1. Store the query tool panels and the list of connections present in each query tool panel and the active connection 2. Store the query that is written in the editor 3. Store the contents of scratch pad We will use debouncing to store the workspace data and all other data related to panels in the pgAdmin 4's configured database file. Through debouncing we will be able to call the API at certain intervals of user interaction, and it will update the stored data related to workspace and all other panels. Kindly share your inputs/suggestions. Thanks Anil -- *Anil Sahoo* Software Engineer www.enterprisedb.com Power to Postgres --0000000000004076b7061f761324 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Hackers,


This feature=C2=A0<= a href=3D"https://github.com/pgadmin-org/pgadmin4/issues/3319" style=3D"fon= t-family:arial,sans-serif">#3319, demands the Workspace and the Query tool panel to be saved before e= xiting the application and on restart it will show earlier opened panels.


We are already saving the = Browser layout, Query tool layout and the Object explorer tree state but to= save the contents of panels we will initially start with the Query tool. T= he below implementation will be done,

  1. Store the query tool pan= els and the list of connections present in each query tool panel and the ac= tive connection
  2. Store the query that is = written in the editor
  3. Store the contents of sc= ratch pad


We will use debouncing to = store the workspace data and all other data related to panels in the pgAdmi= n 4's configured database file. Through debouncing we will be able to c= all the API at certain intervals of user interaction, and it will update th= e stored data related to workspace and all other panels.


Kindly share yo= ur inputs/suggestions.


Thanks

Anil

--

Anil Sahoo<= /b>

Software Engineer

= www.ent= erprisedb.com

Power to Postgres

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0

--0000000000004076b7061f761324--