Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-devel] Clarifications on Legend View Spec - Sorting Clarification

With the discussions below, I would just like to summarize everything:

·         ‘Natural Ordering ‘ will only be applied when adding a new layer

·         Move up/down will follow the ordering logic used by Layer View

·         Move to front/back will move the layer on top/below of everything, irregardless of layer type

·         As discussed with Mark, the logic to use “keywords” was scrapped before  due to time constraints and  this will not be implemented.

 

Thanks!

 

From: udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jody Garnett
Sent: Wednesday, 15 February 2012 10:56 PM
To: User-friendly Desktop Internet GIS
Cc: Paul Pfeiffer
Subject: Re: [udig-devel] Clarifications on Legend View Spec - Sorting Clarification

 

As long as we are considering options; when adding a layer we could consider a sensible default folder location for the new layer based on any associated "keywords".

Probably find the layer that has the most matching keywords and put the new layer next to it?

 

Jody

 

On 15/02/2012, at 9:52 PM, Jody Garnett wrote:



I was only considering this default ordering thing when *adding* a new layer.

 

basically drop it in from the top and let it "sink" until it hits something that stops it.

 

Consider the following base:

 

ggppllyyrr

 

Adding a P

ggPppllyyrr

 

Adding a L

ggppLllyyrr

 

Adding a Y

ggppllYyyrr

 

Adding a R

ggppllyyrrR

 

I also congratulate you on your use of ascii art; it has brightened my day.

 

For the move up / move down tools we are just fussing with zorder. If move to front and move to back don't make sense kill them as a bad idea.

 

Jody

 

On 15/02/2012, at 8:36 AM, Mark Leslie wrote:



So there are two examples that spring to mind that foil with the zorder tools we're looking at.  To asciiify Naz's diagram, the normal case looks something like:

 

ggpppplllLllyyyyrrrrr

 

for g=mapgraphic, p=point, l=line, y=polygon, r=raster.  Hitting move to top on the capital L leads to:

 

ggppppLlllllyyyyrrrrr

 

That makes sense.  But the next two examples are less nice.

 

1 - ggpplppllLlyyyyrrrr

2 - ggppplllLlyypyyrrrr

 

Essentially, the described behaviour of moving the L line to the top of the lines breaks down in these cases.  There are two ways to look at this, A. move L to be above the first line or B. move L to be below the last point.

 

1A - ggppLlpplllyyyyrrrr

1B - ggpplppLlllyyyyrrrr

2A - ggpppLllllyypyyrrrr

2B - ggpppllllyypLyyrrrr

 

I was thinking to do something that doesn't quite meet the description of the tool, and move the layer to the top of it's current, continuous block of like layers:

 

1 - ggpplppLlllyyyyrrrr

2 - ggpppLllllyypyyrrrr

 

The downsides of that being the case where the selected layer is the outlier:

 

before - ggppppllllyyLyyrrrr

after - ggppppllllyyLyyrrrr

 

...and the difficulty in explaining what is happening in the tool tip.

 

Thoughts?

 

On 14 February 2012 21:50, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

Correct; that is basically the ordering which allows the "most" content to be visible. So when adding a new layer; it should sift down into the right spot by default.

 

You are correct that people can mess with the zorder (i.e. drawing order) after the layer has been added; this natural ordering is an application of the uDig Guideline "Sensible default".

 

-- 

Jody Garnett

 

On Tuesday, 14 February 2012 at 3:19 PM, Nazareno Chan wrote:

Hi Guys,

 

Just wanna clarify some details regarding the ‘natural sorting’ to be implemented on Legend View:

 

1.       Is the diagram below correct regarding the natural ordering of layers?

2.       Noting that using the Layers View, the user can rearrange the layers anyway they want, irregardless or natural ordering:

§  For example, moving a line layer to the front, do we look for the lowest point layer and move it below this? Or the highest line layer and move it above this?

§  If the lowest point layer was placed below the lines? Or the highest line layer above the points?

 

<image002.png>

 

Thanks,

Naz Chan

 


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

_______________________________________________

User-friendly Desktop Internet GIS (uDig)

 


_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel



 

--
Mark Leslie
Geospatial Software Architect
LISAsoft

-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------

LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com

 

<ATT00001.c>

 



The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

Back to the top