Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d3d6A-0001ZI-Kj for pgadmin-hackers@arkaria.postgresql.org; Thu, 27 Apr 2017 06:40:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d3d69-0002L2-IQ for pgadmin-hackers@arkaria.postgresql.org; Thu, 27 Apr 2017 06:40:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d3d5v-0001si-5R for pgadmin-hackers@postgresql.org; Thu, 27 Apr 2017 06:40:03 +0000 Received: from mail-wr0-x22f.google.com ([2a00:1450:400c:c0c::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d3d5q-0006f3-PE for pgadmin-hackers@postgresql.org; Thu, 27 Apr 2017 06:40:02 +0000 Received: by mail-wr0-x22f.google.com with SMTP id l9so11228553wre.1 for ; Wed, 26 Apr 2017 23:39:58 -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:from:date:message-id:subject:to :cc; bh=vhZmxfvDq8UHLkR+uzRxNO/mjH0I+NVSUxvE01FHNJQ=; b=Y3PIp23DxZd3Exyl6y2EAN0TlZxXtxJYEdBIdm9QccON8oMxTO2zEuFY3q/V6c4UEr mk2q4zSx+tuToeSAAwLT8tfdwLJIYUie/p+qbV9RjmplJwr+VquYh1iDDwqQFCwlvObo 2Y60BybdB9YNiG4n72UrpWVJOORFYEtHFrt6C/8Zw16RJiBffm1pTEqBk9SPrWreKkC0 99a7alZabuBcN8EavtiAJ4g5C4tvMi4bamEeV9BPQ+dLele7HfOzS4J7gas+4JTfKSel RFYaACghk3qoYSsh38tCbkd3YcclEXGX79N7+NvxZVTDH4G7quvCwZZYIu506BT/JJVo GdlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vhZmxfvDq8UHLkR+uzRxNO/mjH0I+NVSUxvE01FHNJQ=; b=BHSdKzMDqR73DEihuj2KO42QQcehH1M1q4cJKRg8IrDpjuP2k09pzEn9z1XuIcy51W 2w3kmsQK8LlSkkmrLbxi0CbCsuir0V+ndLNGGPdkPQKt22J+gdeu/2xQgBGApbN6Csd4 uovb/DKlxC2N6ELckFLJQbOVze5t5gB+OGQmeSAcj79WA63h/Az3SxQCOOXX+7v6atin fyDoFDXhf1vrV8QTsW8LAbhUTLkpiFMn8QzOhADAI9ohJKO0lM/Rk0qOMYJMQGUf8Rhh 0dNVKpUjYSntwuRd/d8a3LjFdp5k0YBlivg4IcKIemnHoao7diLPCWA4cibfqAUV4nKJ 7hug== X-Gm-Message-State: AN3rC/7/wL5tbICVgmYRlhhVLVEPL1Jxd3bXynBWILLs1R390VoAYp0p RKdkVmA2GCHWu4gfjEgwwUYx22iPn03v X-Received: by 10.223.139.150 with SMTP id o22mr1605383wra.118.1493275197282; Wed, 26 Apr 2017 23:39:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.136.70 with HTTP; Wed, 26 Apr 2017 23:39:36 -0700 (PDT) In-Reply-To: References: From: Murtuza Zabuawala Date: Thu, 27 Apr 2017 12:09:36 +0530 Message-ID: Subject: Re: Issue with SlickGrid To: Joao Pedro De Almeida Pereira Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=f403045e9cd0afae92054e2039f8 X-Pg-Spam-Score: -1.9 (-) 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 --f403045e9cd0afae92054e2039f8 Content-Type: text/plain; charset=UTF-8 Hello Joao, Yes, We made some changes in SlickGrid library when we integrated it into Query tool. *Issue:* Last row from the query result set was not displaying correctly in query tool when we have scrollbar in grid. The row hight/width pixel size calculations is done inside SlickGrid javascript code, Though we tried solve it through CSS but we had no luck, so we had no other choice but to do it in library it self. The changes were, 1) "getDataLengthIncludingAddNew()" function (slick.grid.js) to add two new rows instead of one when user add values into row (one row is dummy & not visible to user so that it displays last row correctly) 2) Other change was done into "appendRowHtml()" function to calculating the correct number of rows in SlickGrid result as we have added our own custom row as mentioned earlier. 3) Abbreviated long CSS classes as mentioed in README file. Apologies we missed to update this change in README. -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Thu, Apr 27, 2017 at 2:23 AM, Joao Pedro De Almeida Pereira < jdealmeidapereira@pivotal.io> wrote: > Hello Hackers, > > While doing some changes to the Query Results we found out that there was > a issue with Slick grid. > > The issue that we found was with the CellSelectModel, behaved differently > when pressing Ctrl and Command(Mac). We created a PR > with the change to changes > the behavior of the plugin. > > When this PR is applied to the SlickGrid library we need to apply it to > the current version of SlickGrid that we have vendorized. > According to the libraries.txt file we are in version 2.2.4 of the library > but a diff between our code and the libraries version 2.2.4 shows > differences in the code. > > Did we do any change to SlickGrid library that is vendorized? Or is just > the information in libraries.txt that is incorrect? > Does anyone know any problem if we bump the version of SlickGrid to the > newer version after the PR is applied? > > Thanks > Joao > --f403045e9cd0afae92054e2039f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Joao,

Yes, We made some changes i= n SlickGrid library when we integrated it into Query tool.

Issue: Last row from the query result set was not displayin= g correctly in query tool when we have scrollbar in grid.
The row hight/width pixel size calculations is done inside= SlickGrid javascript code, Though we tried solve it through CSS but we had= no luck, so we had no other choice but to do it in library it self.
<= /div>
=C2=A0=C2=A0
The changes were,
1) "g= etDataLengthIncludingAddNew()" function (slick.grid.js) to add tw= o new rows instead of one when user add values into row (one row is dummy &= amp; not visible to user so that it displays last row correctly)
= 2) Other change was done into "appendRowHtml()" function to calcu= lating the correct number of rows in SlickGrid result as we have added our = own custom row as mentioned earlier.
3) Abbreviated long CSS clas= ses as mentioed in README file.
=C2=A0
Apologies w= e missed to update this change in README.

<= div class=3D"gmail_extra">
--=
Regards,
Murtuza Zabuawala
Enterpri= seDB:=C2=A0http://www.enterprisedb= .com
The Enterprise PostgreSQL Company


On Thu, Apr 27, 2017 at 2:23 AM, Joao Pedro = De Almeida Pereira <jdealmeidapereira@pivotal.io>= wrote:
Hello Hackers,
While doing some changes to the Query Results we found ou= t that there was a issue with Slick grid.=C2=A0

Th= e issue that we found was with the CellSelectModel, behaved differently whe= n pressing Ctrl and Command(Mac). We created a PR with the change to chan= ges the behavior of the plugin.

When this PR is ap= plied to the SlickGrid library we need to apply it to the current version o= f SlickGrid that we have vendorized.
According to the libraries.t= xt file we are in version 2.2.4 of the library but a diff between our code = and the libraries version 2.2.4 shows differences in the code.
Did we do any change to SlickGrid library that is vendorized? = Or is just the information in libraries.txt that is incorrect?
Do= es anyone know any problem if we bump the version of SlickGrid to the newer= version after the PR is applied?

Thanks
Joao

--f403045e9cd0afae92054e2039f8--