Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1apbRs-0007bq-Ii for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Apr 2016 13:00:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1apbRr-0007iO-Lz for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Apr 2016 13:00:11 +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 1apbRd-0007SU-JD for pgadmin-hackers@postgresql.org; Mon, 11 Apr 2016 12:59:58 +0000 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1apbRZ-000298-Vu for pgadmin-hackers@postgresql.org; Mon, 11 Apr 2016 12:59:56 +0000 Received: by mail-wm0-x234.google.com with SMTP id v188so85325806wme.1 for ; Mon, 11 Apr 2016 05:59:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=ytT7SFEU2zcA0VcDoy4pXRVpUZ7LePDchqKwiQlNMpU=; b=FXkG3DZjlsGrce1SnuaVTvDmedpzE3W80UjE2W9IfeZYLJ91iRQcLOSXR+A9kqHicT Iv/C9RwuOPTYJW5QwplNFbhbJ3mWC1KO/3woUoaZh4ssQ9nGkw0Pk/3j6vK/NlRpNRwe B7wN55CHhObfeDIyU1tCqgQQFJfVhlOWKSjNjd+84SMF20ztRz1mZUJ5bYMxwHb54V52 6g0euqbDXlmVjMqs9ZvaDk8c+0HQGzZa0pFLuWVgpmedqtrphp/R7QsoG2Hea01BZJDn qEDbIETFyjZAwYZpTp2SJF+Uq8i/vFmLy5fGiH11qD2gGQmiuzea56UkNb0N6yzikioN VSQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ytT7SFEU2zcA0VcDoy4pXRVpUZ7LePDchqKwiQlNMpU=; b=aOIUZg9LwvkUWLhQoYWsGZeMllx+tV6lujpgzEFP0aN2InS376U/M9rQsbb66tIxDO rShepSj/huenL+hhh4Vk+47j3OuYkQxbGS7a7wGPCvnWD9pRTTvzeawhfh66EYBlN+HS Yb1FDae6iyuaVUt24lWCvHaHj3ByleRIXxzqghbgikjo7O8y/LA9FbhBiuzvbyMLe1Jc gM8bf7My2DDWMjxniD7vPlzNu42MpzkKt5wZyALQfy0TrC4vjloOs+usSY+3EFaBdCeT yCLwEbdZTOStylza0hWizduBwefTP9WWc6necUyDzEVFvjlfLBT5q0HPw5Q/Ck9R1NxH 2WGw== X-Gm-Message-State: AD7BkJI1qQJ+gylSNVIS5wdglcOJxJJl1LtH8U4rzGuYSb9VSAvdQKZw1GKGg737j1H5UodU X-Received: by 10.28.49.3 with SMTP id x3mr17771352wmx.4.1460379591886; Mon, 11 Apr 2016 05:59:51 -0700 (PDT) Received: from [172.16.1.31] ([194.73.70.210]) by smtp.gmail.com with ESMTPSA id a73sm17355409wme.2.2016.04.11.05.59.50 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2016 05:59:50 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_7A2FB18B-4958-4A9B-B0AF-004DBBE8B9AA" Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Styling SQL box layout on dialogue From: Arun Kollan In-Reply-To: Date: Mon, 11 Apr 2016 13:59:50 +0100 Cc: "pgadmin-hackers@postgresql.org" Message-Id: <7924AEDF-2F27-409F-9EB5-7252BA14BFCD@enterprisedb.com> References: <69DBED24-ECF2-48A2-94F9-EEED5BAF8C63@enterprisedb.com> <8AFA3AC4-2552-4547-80D5-50981C31EE7E@enterprisedb.com> To: Dave Page X-Mailer: Apple Mail (2.2104) 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 --Apple-Mail=_7A2FB18B-4958-4A9B-B0AF-004DBBE8B9AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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.=20 I am assuming that the screenshot displayed is the dialogue window for = database properties.=20 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: >=20 > Still looks the same as my last screenshot to me. >=20 > 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. >>=20 >>=20 >> Regards, >>=20 >> Arun Kollan >> Website: www.enterprisedb.com >> EnterpriseDB Blog: http://blogs.enterprisedb.com/ >> Follow us on Twitter: http://www.twitter.com/enterprisedb >>=20 >> 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. >>=20 >>=20 >>=20 >>=20 >> On 11 Apr 2016, at 10:45, Arun Kollan = wrote: >>=20 >> Hi Dave, >> Looks the like the patch is out of sync with the repository. I will = create >> another patch now. >>=20 >> Regards, >> Arun Kollan >> Website: www.enterprisedb.com >> EnterpriseDB Blog: http://blogs.enterprisedb.com/ >> Follow us on Twitter: http://www.twitter.com/enterprisedb >>=20 >> 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. >>=20 >>=20 >>=20 >>=20 >> On 11 Apr 2016, at 10:09, Dave Page = wrote: >>=20 >> On Fri, Apr 8, 2016 at 2:23 PM, Arun Kollan >> wrote: >>=20 >> Hi Team, >>=20 >> 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. >>=20 >>=20 >> There still seem to be padding/margin issues on my machine (under >> Chrome). Am I missing something? >>=20 >> -- >> Dave Page >> VP, Chief Architect, Tools & Installers >> EnterpriseDB: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company >>=20 >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake >> >>=20 >>=20 >>=20 >>=20 >=20 >=20 >=20 > --=20 > Dave Page > VP, Chief Architect, Tools & Installers > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company >=20 > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake --Apple-Mail=_7A2FB18B-4958-4A9B-B0AF-004DBBE8B9AA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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 <dave.page@enterprisedb.com> wrote:

Still looks the same = as my last screenshot to me.

On Mon, Apr = 11, 2016 at 11:31 AM, Arun Kollan
<arun.kollan@enterprisedb.com> 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 <arun.kollan@enterprisedb.com> 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 <dave.page@enterprisedb.com> wrote:

On Fri, Apr 8, 2016 at 2:23 PM, Arun Kollan
<arun.kollan@enterprisedb.com> 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
<Screen Shot 2016-04-11 at 10.07.08.png>







-- =
Dave Page
VP, Chief Architect, Tools & = Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise = PostgreSQL Company

Blog: http://pgsnake.blogspot.com
Twitter: = @pgsnake

= --Apple-Mail=_7A2FB18B-4958-4A9B-B0AF-004DBBE8B9AA--