Re: Styling SQL box layout on dialogue

public inbox for [email protected]  
help / color / mirror / Atom feed

From: Arun Kollan <[email protected]>
To: Dave Page <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Styling SQL box layout on dialogue
Date: Mon, 11 Apr 2016 13:59:50 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+OCxoxNzcR9T-cReSxnLD_UzvkQ-zeQYg01HJwgTqZVPkJ2_A@mail.gmail.com>
References: <[email protected]>
	<CA+OCxowJPp5WmawaBWwgribUjmDA9autbB4aiRgDG20GathqCg@mail.gmail.com>
	<CAMVYmSDTuxc5XSh-=13XsUgTjzDOb7Vc8iw8E+WpxjX5nNZMfQ@mail.gmail.com>
	<CA+OCxozGxMmFA96BFBgiMCkEctQSDxi4AXchv3v=CEDuye0cpA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CA+OCxoxNzcR9T-cReSxnLD_UzvkQ-zeQYg01HJwgTqZVPkJ2_A@mail.gmail.com>
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20pgadmin-hackers>

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 <http://www.enterprisedb.com/;
EnterpriseDB Blog: http://blogs.enterprisedb.com/ <http://blogs.enterprisedb.com/;
Follow us on Twitter: http://www.twitter.com/enterprisedb <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 <[email protected]> wrote:
> 
> Still looks the same as my last screenshot to me.
> 
> On Mon, Apr 11, 2016 at 11:31 AM, Arun Kollan
> <[email protected]> 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 <[email protected]> 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 <[email protected]> wrote:
>> 
>> On Fri, Apr 8, 2016 at 2:23 PM, Arun Kollan
>> <[email protected]> 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

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Styling SQL box layout on dialogue
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox