Hi On Wed, Jan 24, 2018 at 7:47 AM, Chethana Kumar < chethana.ku...@enterprisedb.com> wrote:
> Hi Dave, > > Can you please the icons as I have added a differentiating factor for them > now. > I think it's too detailed. If I view it at the typical 64x64 size, then I really can't make it out properly. What about combining ex_index_only_scan with index scan? e.g. replace the lower tree nodes on index_only_scan with two or three table rows to indicate an index scan that then leads to a table access? > > Thanks, > Chethana kumar > > On Mon, Jan 22, 2018 at 4:14 PM, Dave Page <dp...@pgadmin.org> wrote: > >> Hi >> >> On Thu, Jan 18, 2018 at 12:48 PM, Chethana Kumar < >> chethana.ku...@enterprisedb.com> wrote: >> >>> Hello Team, >>> >>> I am sending a patch for the ex_index and ex_scan icons where those were >>> similar to each other so I have made them easy to differentiate now. >>> >>> It is respective to the issue *RM# 3021* >>> >> >> They're still only distinguishable by colour, which isn't good for >> accessibility. Can you think about an alternative design for index scans? >> >> Thanks. >> >> -- >> Dave Page >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake >> >> EnterpriseDB UK: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company >> > > > > -- > Chethana Kumar > Principal UI/UX Designer > EnterpriseDB Corporation > > > The Postgres Database Company > > P: +91 86981 57146 <+91%2086981%2057146> > www.enterprisedb.com > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
