Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aq0fI-0002R9-VW for pgadmin-hackers@arkaria.postgresql.org; Tue, 12 Apr 2016 15:55:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1aq0fI-0004Xe-I6 for pgadmin-hackers@arkaria.postgresql.org; Tue, 12 Apr 2016 15:55:44 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1aq0fH-0004Vf-OV for pgadmin-hackers@postgresql.org; Tue, 12 Apr 2016 15:55:43 +0000 Received: from mail-ig0-x22a.google.com ([2607:f8b0:4001:c05::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1aq0fE-0002Ea-Qf for pgadmin-hackers@postgresql.org; Tue, 12 Apr 2016 15:55:42 +0000 Received: by mail-ig0-x22a.google.com with SMTP id f1so91395437igr.1 for ; Tue, 12 Apr 2016 08:55:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YmKSKh7s5lcDmKwdkDzqzEFAwA4qd51ut0SvBs9Uf+s=; b=bQ8ssN3WcE/QZ6PAL1BbD94lx4pLkSyCjaC++VCu5m7yp7MRPmrEgbiePO/gBcKLpD t3EC6iSFlH067OnnJ4kcazPzhoDOH09l0wRjsD1fqK+iEehGqC5FhDCQWoUD13Av/Oe4 ENAjP8RcpgWRCgmJgBpxHhS60Zw4aNmXeS71ptnJ/Dmbn6fY3OD5l+gwuF4+etH+g6I/ BlTgY1P2TEfbzTK7NSWWeDont07ZXqZw1KwjSPzLx2cfzms/4UwpA4oHTtBShX91mkgj UVFK9F/o26wOvCg7otNnpB0PtxLGlO4UJthO0M6aNWtcP26h9OX2xsFJRZ6HlJ24WfQJ NCmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YmKSKh7s5lcDmKwdkDzqzEFAwA4qd51ut0SvBs9Uf+s=; b=GNsLuXwURKyFPiw9VbzXQWrY0zmO6PIFOHaY1y4Bonxyvv30XAXYdPJxmb0sfVfD8Y NDWNLkOkdOnscxMc+pkYhoHD/XpR9VBYBmOdjL+Q6wc+iBF+AwWueQYGvyTWRxp7+Ay4 779AhikbSiqOBBet3F7ihWjqumU1JTELjSo5ndJd0KPnCR1p/i67smwmU39o4Tzlhha9 xu9/lbnN0UCCXR5fk04h3PSYoTN+KxCutRpAiCvu8ak68yvuloZwPahVdcJUanlhuVDE g+9zWhhkKQnokflS1C4QZcOEatCNU/g4DCYGGRtc8UjP/UOqNyorUVhWOtR7IENoteML geEg== X-Gm-Message-State: AOPr4FX/twF6DvEj827QDA4rTFL0gIUA5XXe320tiQQlfLAY0LyPj7H11nTpBkbqMUDsgIvuE94uWcm1zOWe//yHAQgzihGQN1Js1hT7JhnoG0++gqOV3yUZ1ZdEJ9Z7ova790HcfJslUH/j1bGeZ2utsgggL6IsNYixe2nnWbxYn/I5LbU5XzwWVdax7YCrZwJb4VwJrw== X-Received: by 10.50.144.163 with SMTP id sn3mr24330086igb.26.1460476538387; Tue, 12 Apr 2016 08:55:38 -0700 (PDT) Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id k2sm16027445igx.5.2016.04.12.08.55.36 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 08:55:37 -0700 (PDT) Received: by mail-io0-f169.google.com with SMTP id u185so33768953iod.3 for ; Tue, 12 Apr 2016 08:55:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.56.196 with SMTP id f187mr4904159ioa.156.1460476536509; Tue, 12 Apr 2016 08:55:36 -0700 (PDT) Received: by 10.64.105.131 with HTTP; Tue, 12 Apr 2016 08:55:36 -0700 (PDT) In-Reply-To: <7924AEDF-2F27-409F-9EB5-7252BA14BFCD@enterprisedb.com> References: <69DBED24-ECF2-48A2-94F9-EEED5BAF8C63@enterprisedb.com> <8AFA3AC4-2552-4547-80D5-50981C31EE7E@enterprisedb.com> <7924AEDF-2F27-409F-9EB5-7252BA14BFCD@enterprisedb.com> Date: Tue, 12 Apr 2016 16:55:36 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Styling SQL box layout on dialogue From: Dave Page To: Arun Kollan Cc: "pgadmin-hackers@postgresql.org" Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org OK, taking another look it seems like it's bit-rotted. Can you rebase please? Thanks. piranha:web dpage$ git pull Already up-to-date. piranha:web dpage$ git apply ~/Downloads/sql-box-layout-stylingv2.patch /Users/dpage/Downloads/sql-box-layout-stylingv2.patch:9: trailing whitespace. .pgadmin-controls.SQL { /Users/dpage/Downloads/sql-box-layout-stylingv2.patch:10: trailing whitespace. min-width: 290px; /Users/dpage/Downloads/sql-box-layout-stylingv2.patch:11: trailing whitespace. padding-right: 3px; /Users/dpage/Downloads/sql-box-layout-stylingv2.patch:12: trailing whitespace. padding-left: 1px; /Users/dpage/Downloads/sql-box-layout-stylingv2.patch:13: trailing whitespace. } error: patch failed: web/pgadmin/static/css/overrides.css:276 error: web/pgadmin/static/css/overrides.css: patch does not apply error: patch failed: web/pgadmin/static/js/backform.pgadmin.js:519 error: web/pgadmin/static/js/backform.pgadmin.js: patch does not apply On Mon, Apr 11, 2016 at 1:59 PM, Arun Kollan wrote: > Hi Dave, > I asked Murtuza to apply the patch at his end and test on Chrome and > Firefox. We had a Skype session and it does appear to fix the issue. It > required a hard reload and cache clearing to get it working. > > I am assuming that the screenshot displayed is the dialogue window for > database properties. > > Regards, > Arun Kollan > Website: www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are not > the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you have received > this e-mail in error, please notify the sender immediately by reply e-mail > and delete this message. > > > > > On 11 Apr 2016, at 13:33, Dave Page wrote: > > Still looks the same as my last screenshot to me. > > On Mon, Apr 11, 2016 at 11:31 AM, Arun Kollan > wrote: > > Hi Dave, > Please find attached the zipped version of the patch. I have tested it > against the latest version from the repository. I had quick look comparing > the patches and it looks to contain the same rules. > > > Regards, > > Arun Kollan > Website: www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are not > the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you have received > this e-mail in error, please notify the sender immediately by reply e-mail > and delete this message. > > > > > On 11 Apr 2016, at 10:45, Arun Kollan wrote: > > Hi Dave, > Looks the like the patch is out of sync with the repository. I will create > another patch now. > > Regards, > Arun Kollan > Website: www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are not > the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you have received > this e-mail in error, please notify the sender immediately by reply e-mail > and delete this message. > > > > > On 11 Apr 2016, at 10:09, Dave Page wrote: > > On Fri, Apr 8, 2016 at 2:23 PM, Arun Kollan > wrote: > > Hi Team, > > please find attached the patch for styling the sql editor on a dialogue > window. The separate rule has been written to include the style specific to > a control window. > > > There still seem to be padding/margin issues on my machine (under > Chrome). Am I missing something? > > -- > Dave Page > VP, Chief Architect, Tools & Installers > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > > > > > > > > -- > Dave Page > VP, Chief Architect, Tools & Installers > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > -- Dave Page VP, Chief Architect, Tools & Installers EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company Blog: http://pgsnake.blogspot.com Twitter: @pgsnake -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers