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 1tE2Bm-004jaJ-G1 for pgadmin-hackers@arkaria.postgresql.org; Thu, 21 Nov 2024 08:05:22 +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 1tE2Bk-00DaDK-OK for pgadmin-hackers@arkaria.postgresql.org; Thu, 21 Nov 2024 08:05:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tE2Bk-00DaDC-Ec for pgadmin-hackers@lists.postgresql.org; Thu, 21 Nov 2024 08:05:20 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tE2Bh-0034b5-9q for pgadmin-hackers@postgresql.org; Thu, 21 Nov 2024 08:05:19 +0000 Received: by mail-ot1-x332.google.com with SMTP id 46e09a7af769-71807ad76a8so280675a34.0 for ; Thu, 21 Nov 2024 00:05:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1732176315; x=1732781115; 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=PMu3cF0pPC2CSAHVA5JpvgUJHMBXdKpYZ9D9oMs/FlA=; b=Frr6ItXza1R4lSwy4M1dwdFpDvOlTBFnOKZi0aN6D+G3Dm8qNie7euXbJPFO9am8WQ 6P5GU4S44epvYc17N9kFj5oSz+0czBR2ncPEa2/NJPTBst40QcBhR8xVU4lj0NBcxGs/ JNxcHRpS7Qziab/U44uoACciGgk4EEHtzBHUcnZuapjST8ZVuaYaAmTC2aTn66owX1e8 mHd05mFfFm9fZNh8Rvb1dyXKDbYu/UWAh2ueVjrPV8NJSDvtqkdXk4NKCjCxMDPUdeDQ i4eCV8rzbOuEsyO/xjAW6gKGiy91smOIqKaSO+1uG/t4Nocw7GuXyKpobEd5BJSWtvi/ okPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732176315; x=1732781115; 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=PMu3cF0pPC2CSAHVA5JpvgUJHMBXdKpYZ9D9oMs/FlA=; b=ciRiYDr8RYnip6kWStREgOzNMI1xNJyqABYrfJfJKj2d60gYQX1gsrHpxCZIzPQLrF OIKZfsSsat4+2ZoJxhOnQ8dtTljA1SzxGlUmI9cjQ+imlokjJMnbVhoJQpgCMEaXnZMW 0HcOZfRzkq6cV/9I7i3vRo5EsSQJMBkba+P1emWtHZEmos5lTUOmFnE7Qrc3uhRxOkEz y5zlAD3a5ELSYnjt9QrP5upmY5S0wFwj5mJgL8pX3L2tg2lNT/bdOKNmhgUWkXegjnVF 1wyssL5FerZOCiKuosJTSQppwF5yWRcY94nuay3R0TGmaByT+Zb5ldnm3CaFH0oEQPgg z8+A== X-Gm-Message-State: AOJu0YxXyQ3kE77cQ7qHQlzBjtD/vSu8gBEDc3jq6Nk1x0jg22LiZn+d 62XLnVMfOQDG87dKlmaWt/ZA6fBsZ2Il2BNJaS4Ovm9eySsQdkx8O2sUo3llw2MgSJhYPM2nwfY WH+GeLoRHZTX+Wn9ilJGw3gHGJD4bkW5SaGirSWKYNfTXzuo= X-Google-Smtp-Source: AGHT+IEb5IrVJ205WcN3qyD5XeuZlfWnCmVAUyMLWLd9FjUDcJ56EZdXNX5mAAuJ1wjKugmLEHButoaGcZSISuIoaZU= X-Received: by 2002:a9d:590b:0:b0:718:5bed:3596 with SMTP id 46e09a7af769-71ab31c3950mr4615329a34.15.1732176314756; Thu, 21 Nov 2024 00:05:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Pravesh Sharma Date: Thu, 21 Nov 2024 13:35:03 +0530 Message-ID: Subject: Re: Require suggestion for issue #6513 To: Rohit Bhati Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="000000000000ee1622062767b9ff" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ee1622062767b9ff Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rohit, In the disconnect database dialog, the button label should be disconnect not delete. Thanks, Pravesh On Thu, Nov 21, 2024 at 1:18=E2=80=AFPM Rohit Bhati wrote: > Hi Hackers, > > I have been working on issue #6513 > and have > implemented some changes based on user suggestions. Here=E2=80=99s a summ= ary of the > modifications I made locally: > > 1. *Button Label Changes*: > - Updated the labels of the buttons to "Delete" or "Disconnect" for > affirmative actions. > - Changed the label "No" to "Cancel" for negative actions. > 2. *Icon Additions*: > - Added appropriate icons for the "Disconnect" and "Delete" actions= . > > I would like your input on whether these changes should be applied > universally across all delete and disconnect scenarios, or if they should > be limited to just the database delete and disconnect actions. > > Please find the attached screenshots showcasing the changes. > > > Thank you for your feedback! > > Best regards, > Rohit Bhati > > > --000000000000ee1622062767b9ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Rohit,

In the disconnect databa= se dialog, the button label should be disconnect not delete.

=
Thanks,
Pravesh

On Thu, Nov 21, 2024 at 1:18=E2= =80=AFPM Rohit Bhati <ro= hit.bhati@enterprisedb.com> wrote:

Hi Hackers,

I have been working on issue #6513 and have i= mplemented some changes based on user suggestions. Here=E2=80=99s a summary= of the modifications I made locally:

  1. But= ton Label Changes:
    • Updated the labels of the buttons to= "Delete" or "Disconnect" for affirmative actions.
    • Changed the label "No" to = "Cancel" for negative actions.
  2. Ico= n Additions:
    • Added appropriate icons for the &quo= t;Disconnect" and "Delete" actions.

I = would like your input on whether these changes should be applied universall= y across all delete and disconnect scenarios, or if they should be limited = to just the database delete and disconnect actions.

Please find the att= ached screenshots showcasing the changes.


Thank you for your feedback!

<= p style=3D"color:rgb(0,0,0)">

Best regards,
Rohit Bhati

=C2=A0

--000000000000ee1622062767b9ff--