OSGeo.org › OSGeo Software and Data Projects › MapGuide Open Source › MapGuide Internals

RFC 81 is ready for review

17 messages

hubu

RFC 81 is ready for review

Reply Threaded

Hi All,

The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
Any comments will be appreciated.

Thanks,
-Buddy Hu
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Kenneth Skovhede, GEOGRAF A/S

Re: RFC 81 is ready for review

Reply Threaded

This overlaps a bit with RFC 71:
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc71

At least the tree for display in the AJAX viewer should be present
there, and I belive Jackie has developed this already?

There is a slight spelling error in the "Inverse selection" menu item.

Are there any changes required in the server code, or is this done with
the current selection system?

There has been questions about the order of properties, some want them
sorted, some want them as is, will there be an option to select sort modus?

To use GZip compression, is it possible to just serve the .gz file or
does it require a webserver change to supply the compression header?
I seem to recal that some browsers do not support GZip compression, and
the served file should obey the compression flag to ensure compatibility.

If a webserver change is required, will the change include maintenance
for the installer?

The test plan should include testing with a range of browsers.

I am overall positive, the preview looks cool, and the addition is
sorely needed.

Regards, Kenneth Skovhede, GEOGRAF A/S

Buddy Hu skrev:

> Hi All,
>
> The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
> Any comments will be appreciated.
>
> Thanks,
> -Buddy Hu
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jackie Ng

Re: RFC 81 is ready for review

Reply Threaded

In reply to this post by hubu

I am a bit miffed that this RFC effectively invalidates most, if not all the work I've done so far on RFC71

But having said that, this looks to be a superior solution, not to mention also that my real life priorities have changed somewhat, grinding my dev. work on RFC71 to a halt.

- Jackie

Buddy Hu wrote:

Hi All,

The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
Any comments will be appreciated.

Thanks,
-Buddy Hu
_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Dave Wilson

RE: RFC 81 is ready for review

Reply Threaded

I also think there should be a mechanism that allows the user to select a feature from the set and it's highlight color should be different. If there are 5 parcels selected the user can pick one from the tree and it is highlighted Red for example instead of blue so that it is easily distinguished from the others.

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Friday, August 21, 2009 3:20 AM
To: [hidden email]
Subject: Re: [mapguide-internals] RFC 81 is ready for review

I am a bit miffed that this RFC effectively invalidates most, if not all the
work I've done so far on RFC71

But having said that, this looks to be a superior solution, not to mention
also that my real life priorities have changed somewhat, grinding my dev.
work on RFC71 to a halt.

- Jackie

Buddy Hu wrote:

>
> Hi All,
>
> The RFC 81- Add a new widget Feature Inspector is ok for review.
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
> Any comments will be appreciated.
>
> Thanks,
> -Buddy Hu
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>

--
View this message in context: http://n2.nabble.com/RFC-81-is-ready-for-review-tp3485127p3487404.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Trevor Wekel

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by hubu

It seems to me that the layer/feature tree view would be a logical replacement for the Properties pane in both the Ajax and Fusion viewers. If there are bandwidth issues with pulling all the feature properties at once, the following mechanism could be employed:

If only a single feature is selected, the entire tree would be initially expanded. If multiple features are selected, only the layers with their feature counts would be visible.

As Dave suggested, a secondary selection color based on the selected item(s) in the tree view could also be a useful feature as it would reduce mouse clicks while the user tries to find the feature he is interested in.

With the secondary highlight "select, select, select, select, turn off check box, invert checked" (6 clicks) would select only the desired feature. With the current implementation, "turn off, turn on, turn off, turn on, turn off, turn on, turn off, invert checked" (8 clicks) would select only the desired feature. The secondary highlight will also take less time to draw than rendering the modified selection each time.

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Buddy Hu
Sent: August 20, 2009 11:42 PM
To: [hidden email]
Subject: [mapguide-internals] RFC 81 is ready for review

Hi All,

The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
Any comments will be appreciated.

Thanks,
-Buddy Hu
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

hubu

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Dave Wilson

Hi Dave,

Thanks for your reply!
Your suggestion is valuable for me. It's ideal if we can highlight the features in different color.
However, as I know, we can't support different highlight color with current API. Do you know whether we have this API to support the different highlight color?

Thanks,
-Buddy Hu

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Friday, August 21, 2009 10:18 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC 81 is ready for review

I also think there should be a mechanism that allows the user to select a feature from the set and it's highlight color should be different. If there are 5 parcels selected the user can pick one from the tree and it is highlighted Red for example instead of blue so that it is easily distinguished from the others.

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Friday, August 21, 2009 3:20 AM
To: [hidden email]
Subject: Re: [mapguide-internals] RFC 81 is ready for review

I am a bit miffed that this RFC effectively invalidates most, if not all the
work I've done so far on RFC71

But having said that, this looks to be a superior solution, not to mention
also that my real life priorities have changed somewhat, grinding my dev.
work on RFC71 to a halt.

- Jackie

Buddy Hu wrote:

hubu

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Jackie Ng

Hi Jackie,

Actually, we will not make any changes to the existing Selection Panel. So I don't think this RFC will impact yours, although there are some functionality overlap.

Thanks,
-Buddy Hu

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Friday, August 21, 2009 5:20 PM
To: [hidden email]
Subject: Re: [mapguide-internals] RFC 81 is ready for review

I am a bit miffed that this RFC effectively invalidates most, if not all the
work I've done so far on RFC71

But having said that, this looks to be a superior solution, not to mention
also that my real life priorities have changed somewhat, grinding my dev.
work on RFC71 to a halt.

- Jackie

Buddy Hu wrote:

hubu

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Kenneth Skovhede, GEOGRAF A/S

Hi Kenneth, Thanks for your reply!

About the overlap with RFC 71, I think we don't make any changes to the existing Selection Panel. If Jackie want to introduce the Selection Panel to the AJAX view, I am pleasure to see this happens. If not, I think the Feature Inspector panel will cover some functionalities of the Selection Panel.

For the typo of "Inverse Selection", I will update it later. Thanks for your good catch.

And I don't think we need any server or Webserver code changes for this RFC. I will clarify these in the "Implications" part.

And I'm not intent to support the sort or filter for the properties now.

For the Gzip, we get this suggestion from Paul Spencer. I didn't do any test for this yet. For more details, you can check the mail I attached.

Thanks for your reply again! I will update my RFC and post it again.

-Buddy

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Friday, August 21, 2009 4:04 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RFC 81 is ready for review

This overlaps a bit with RFC 71:
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc71

At least the tree for display in the AJAX viewer should be present
there, and I belive Jackie has developed this already?

There is a slight spelling error in the "Inverse selection" menu item.

Are there any changes required in the server code, or is this done with
the current selection system?

There has been questions about the order of properties, some want them
sorted, some want them as is, will there be an option to select sort modus?

To use GZip compression, is it possible to just serve the .gz file or
does it require a webserver change to supply the compression header?
I seem to recal that some browsers do not support GZip compression, and
the served file should obey the compression flag to ensure compatibility.

If a webserver change is required, will the change include maintenance
for the installer?

The test plan should include testing with a range of browsers.

I am overall positive, the preview looks cool, and the addition is
sorely needed.

Regards, Kenneth Skovhede, GEOGRAF A/S

Buddy Hu skrev:

_______________________________________________

mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

hubu

答复: RFC 81 is ready for review

Reply Threaded

In reply to this post by Dave Wilson

Hi Dave,

There are some update for this questions:

This function is for SELECTING features in following case:
1. In some case, it's not possible or very difficult to distinguish some features VISUALLY on the map (they are either overlapped or too close with each other)
2. So the user has to distinguish the features by reading their attributes
3. After distinguished the features by checking the attributes, the user should be able to easily make the “wanted” feature(s) selected

Given the item 1 above, we can see, "highlight the feature in a different color" doesn't really help us that much, because we already know it's not possible to distinguish them VISUALLY on the Map (otherwise, we don’t need the inspector, we just zoom and pan to the right feature on the map and select it)

Normally the "select" action will be followed by another action, E.g. bring up a dialog containing the very detail information about selected feature etc. We should consider this case: The user happened to select a wrong feature even after he already read the attributes. Then he should be able to back to the "set" he just made and select the right one he wanted. In our design, the click on the "Inspector Tree" will trigger select action on the Map, but any "selection set" change will NOT trigger any refresh on the "Feature Inspector" AUTOMATICALLY. This way we can keep the "original selection set" in our tree so that the user could change the selected feature(s) back and forth. It’s the difference between the "Feature Inspector" and the existing "Selection Panel". Or we can say "Feature Inspector" is "tree driven", and "Selection Panel" is "map driven".

So I don't think we need the "highlight the feature in a different color".

Thanks again!
-Buddy Hu

________________________________________

Hi Dave,

Thanks for your reply!
Your suggestion is valuable for me. It's ideal if we can highlight the features in different color.
However, as I know, we can't support different highlight color with current API. Do you know whether we have this API to support the different highlight color?

Thanks,
-Buddy Hu

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Friday, August 21, 2009 10:18 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC 81 is ready for review

I also think there should be a mechanism that allows the user to select a feature from the set and it's highlight color should be different. If there are 5 parcels selected the user can pick one from the tree and it is highlighted Red for example instead of blue so that it is easily distinguished from the others.

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Friday, August 21, 2009 3:20 AM
To: [hidden email]
Subject: Re: [mapguide-internals] RFC 81 is ready for review

I am a bit miffed that this RFC effectively invalidates most, if not all the
work I've done so far on RFC71

But having said that, this looks to be a superior solution, not to mention
also that my real life priorities have changed somewhat, grinding my dev.
work on RFC71 to a halt.

- Jackie

Buddy Hu wrote:

hubu

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Trevor Wekel

Thank Trevor for your reply!

I don't think we have a bandwidth issue. These attributes have been requested when the features were selected, we just use these attributes. So this new feature won't add any request to the MapGuide Server. And this feature is available for the user to select 20 or 30 features most on the map. If the user select hundreds of features, it's not a typical use of this "Feature Inspector" panel.

About the secondary highlight, I have reply it in the last mail. I don't think we need it. Because we can't use the highlight to distinguish the feature.And I need to clarify the requirement again, maybe it's not so clear in the RFC:

Basically, this function is for SELECTING features in following case:
1. In some case, it’s not possible or very difficult to distinguish some features VISUALLY on the map (they are either overlapped or too close with each other)
2. So the user has to distinguish the features by reading their attributes
3. After distinguished the features by checking the attributes, the user should be able to easily make the “wanted” feature(s) selected

Given the item 1 above, we can see, “highlight the feature in a different color” doesn’t really help us that much, because we already know it’s not possible to distinguish them VISUALLY on the Map (otherwise, we don’t need the inspector, we just zoom and pan to the right feature on the map and select it).

And with the current disign, we don't need "turn off, turn on, turn off, turn on, turn off, turn on, turn off, invert checked" (8 clicks) to get what we want.
We just read the attributes of feature in the tree, distinguish what we want by these attributes and click what we want.

Thanks,
-Buddy Hu

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Saturday, August 22, 2009 12:25 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: RFC 81 is ready for review

It seems to me that the layer/feature tree view would be a logical replacement for the Properties pane in both the Ajax and Fusion viewers. If there are bandwidth issues with pulling all the feature properties at once, the following mechanism could be employed:

If only a single feature is selected, the entire tree would be initially expanded. If multiple features are selected, only the layers with their feature counts would be visible.

As Dave suggested, a secondary selection color based on the selected item(s) in the tree view could also be a useful feature as it would reduce mouse clicks while the user tries to find the feature he is interested in.

With the secondary highlight "select, select, select, select, turn off check box, invert checked" (6 clicks) would select only the desired feature. With the current implementation, "turn off, turn on, turn off, turn on, turn off, turn on, turn off, invert checked" (8 clicks) would select only the desired feature. The secondary highlight will also take less time to draw than rendering the modified selection each time.

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Buddy Hu
Sent: August 20, 2009 11:42 PM
To: [hidden email]
Subject: [mapguide-internals] RFC 81 is ready for review

Hi All,

The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
Any comments will be appreciated.

Thanks,
-Buddy Hu
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Traian Stanev

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by hubu

Theoretically, you should be able to render with two different selection colors: the RenderDynamicOverlay allows you to render just the selection and also allows you to set the selection color. Do a render of the secondary selection set with blue and then a second render with the primary selected item as red or yellow or whatever.

However, there would be a performance hit due to rendering twice.

Traian

> -----Original Message-----
> From: [hidden email] [mailto:mapguide-internals-
> [hidden email]] On Behalf Of Buddy Hu
> Sent: Monday, August 24, 2009 9:36 AM
> To: MapGuide Internals Mail List
> Subject: 答复: [mapguide-internals] RFC 81 is ready for review
>
> Hi Dave,
>
> There are some update for this questions:
>
> This function is for SELECTING features in following case:
> 1. In some case, it's not possible or very difficult to distinguish
> some features VISUALLY on the map (they are either overlapped or too close
> with each other)
> 2. So the user has to distinguish the features by reading their
> attributes
> 3. After distinguished the features by checking the attributes, the
> user should be able to easily make the “wanted” feature(s) selected
>
> Given the item 1 above, we can see, "highlight the feature in a different
> color" doesn't really help us that much, because we already know it's not
> possible to distinguish them VISUALLY on the Map (otherwise, we don’t need
> the inspector, we just zoom and pan to the right feature on the map and
> select it)
>
> Normally the "select" action will be followed by another action, E.g. bring
> up a dialog containing the very detail information about selected feature
> etc. We should consider this case: The user happened to select a wrong
> feature even after he already read the attributes. Then he should be able to
> back to the "set" he just made and select the right one he wanted. In our
> design, the click on the "Inspector Tree" will trigger select action on the
> Map, but any "selection set" change will NOT trigger any refresh on the
> "Feature Inspector" AUTOMATICALLY. This way we can keep the "original
> selection set" in our tree so that the user could change the selected
> feature(s) back and forth. It’s the difference between the "Feature
> Inspector" and the existing "Selection Panel". Or we can say "Feature
> Inspector" is "tree driven", and "Selection Panel" is "map driven".
>
> So I don't think we need the "highlight the feature in a different color".
>
> Thanks again!
> -Buddy Hu
>
> ________________________________________
>
> Hi Dave,
>
> Thanks for your reply!
> Your suggestion is valuable for me. It's ideal if we can highlight the
> features in different color.
> However, as I know, we can't support different highlight color with current
> API. Do you know whether we have this API to support the different highlight
> color?
>
> Thanks,
> -Buddy Hu
>
> -----Original Message-----
> From: [hidden email] [mailto:mapguide-internals-
> [hidden email]] On Behalf Of Dave Wilson
> Sent: Friday, August 21, 2009 10:18 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RFC 81 is ready for review
>
> I also think there should be a mechanism that allows the user to select a
> feature from the set and it's highlight color should be different. If there
> are 5 parcels selected the user can pick one from the tree and it is
> highlighted Red for example instead of blue so that it is easily
> distinguished from the others.
>
> Dave
>
> -----Original Message-----
> From: [hidden email] [mailto:mapguide-internals-
> [hidden email]] On Behalf Of Jackie Ng
> Sent: Friday, August 21, 2009 3:20 AM
> To: [hidden email]
> Subject: Re: [mapguide-internals] RFC 81 is ready for review
>
>
> I am a bit miffed that this RFC effectively invalidates most, if not all the
> work I've done so far on RFC71
>
> But having said that, this looks to be a superior solution, not to mention
> also that my real life priorities have changed somewhat, grinding my dev.
> work on RFC71 to a halt.
>
> - Jackie
>
>
> Buddy Hu wrote:
> >
> > Hi All,
> >
> > The RFC 81- Add a new widget Feature Inspector is ok for review.
> > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
> > Any comments will be appreciated.
> >
> > Thanks,
> > -Buddy Hu
> > _______________________________________________
> > mapguide-internals mailing list
> > [hidden email]
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> >
> >
>
> --
> View this message in context: http://n2.nabble.com/RFC-81-is-ready-for-
> review-tp3485127p3487404.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jackie Ng

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by hubu

There's no point in having redundant functionality. This RFC seems to cover RFC 71 and more. I have no qualms about suspending/cancelling my work on RFC 71.

- Jackie

Buddy Hu wrote:

Hi Kenneth, Thanks for your reply!

About the overlap with RFC 71, I think we don't make any changes to the existing Selection Panel. If Jackie want to introduce the Selection Panel to the AJAX view, I am pleasure to see this happens. If not, I think the Feature Inspector panel will cover some functionalities of the Selection Panel.

For the typo of "Inverse Selection", I will update it later. Thanks for your good catch.

And I don't think we need any server or Webserver code changes for this RFC. I will clarify these in the "Implications" part.

And I'm not intent to support the sort or filter for the properties now.

For the Gzip, we get this suggestion from Paul Spencer. I didn't do any test for this yet. For more details, you can check the mail I attached.

Thanks for your reply again! I will update my RFC and post it again.

-Buddy

-----Original Message-----
From: mapguide-internals-bounces@lists.osgeo.org [mailto:mapguide-internals-bounces@lists.osgeo.org] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Friday, August 21, 2009 4:04 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RFC 81 is ready for review

This overlaps a bit with RFC 71:
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc71

At least the tree for display in the AJAX viewer should be present
there, and I belive Jackie has developed this already?

There is a slight spelling error in the "Inverse selection" menu item.

Are there any changes required in the server code, or is this done with
the current selection system?

There has been questions about the order of properties, some want them
sorted, some want them as is, will there be an option to select sort modus?

To use GZip compression, is it possible to just serve the .gz file or
does it require a webserver change to supply the compression header?
I seem to recal that some browsers do not support GZip compression, and
the served file should obey the compression flag to ensure compatibility.

If a webserver change is required, will the change include maintenance
for the installer?

The test plan should include testing with a range of browsers.

I am overall positive, the preview looks cool, and the addition is
sorely needed.

Regards, Kenneth Skovhede, GEOGRAF A/S

Buddy Hu skrev:
> Hi All,
>
> The RFC 81- Add a new widget Feature Inspector is ok for review. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
> Any comments will be appreciated.
>
> Thanks,
> -Buddy Hu
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Dave Wilson

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Traian Stanev

Thanks for the feedback guys.

It is not clear to me if the purpose of this RFC is to partially support the concept of deep selection or if we are still only selecting the topmost features. If that is the case then the overlap can only come from objects on top and the secondary highlight should still help as it would be rendered last unless the object is entirely underneath another or the features are identical. There will be issues with points and lines.

If the idea that zoom to selection is the solution instead of a secondary highlight then we need to fix the logic for zooming to selection to properly deal with points and lines. Currently point selection zooms in to 1:0.001 because a point has no envelope. Lines may also have an issue because their envelope may be too large to zoom to particularly for the layer's scale range or if they are entirely vertical or horizontal because you have an envelope with no height or width.

Trevor and I made an attempt to address this with some fixes that never got released by first determining if the object being zoomed to was visible at the current scale (selection may have come from an API search request and the layer may not be visible yet), we then attempted to center the object and zoom to the midpoint of the layer's scale range. If the feature was already visible then we didn't zoom but center. This may not be 100 ideal if the feature is a point that is densely packed near other points. We may need to zoom further in.

Unfortunately Autodesk had some concern as they would like the selection/zooming behavior to work similarly in Map 3d.

I'm not sure how we should try to address this.

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Traian Stanev
Sent: Monday, August 24, 2009 8:41 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC 81 is ready for review

Theoretically, you should be able to render with two different selection colors: the RenderDynamicOverlay allows you to render just the selection and also allows you to set the selection color. Do a render of the secondary selection set with blue and then a second render with the primary selected item as red or yellow or whatever.

However, there would be a performance hit due to rendering twice.

Traian

> -----Original Message-----
> From: [hidden email]
> [mailto:mapguide-internals- [hidden email]] On Behalf Of
> Buddy Hu
> Sent: Monday, August 24, 2009 9:36 AM
> To: MapGuide Internals Mail List
> Subject: 答复: [mapguide-internals] RFC 81 is ready for review
>
> Hi Dave,
>
> There are some update for this questions:
>
> This function is for SELECTING features in following case:
> 1. In some case, it's not possible or very difficult to distinguish
> some features VISUALLY on the map (they are either overlapped or too
> close with each other)
> 2. So the user has to distinguish the features by reading their
> attributes
> 3. After distinguished the features by checking the attributes, the
> user should be able to easily make the “wanted” feature(s) selected
>
> Given the item 1 above, we can see, "highlight the feature in a
> different color" doesn't really help us that much, because we already
> know it's not possible to distinguish them VISUALLY on the Map
> (otherwise, we don’t need the inspector, we just zoom and pan to the
> right feature on the map and select it)
>
> Normally the "select" action will be followed by another action, E.g.
> bring up a dialog containing the very detail information about
> selected feature etc. We should consider this case: The user happened
> to select a wrong feature even after he already read the attributes.
> Then he should be able to back to the "set" he just made and select
> the right one he wanted. In our design, the click on the "Inspector
> Tree" will trigger select action on the Map, but any "selection set"
> change will NOT trigger any refresh on the "Feature Inspector"
> AUTOMATICALLY. This way we can keep the "original selection set" in
> our tree so that the user could change the selected
> feature(s) back and forth. It’s the difference between the "Feature
> Inspector" and the existing "Selection Panel". Or we can say "Feature
> Inspector" is "tree driven", and "Selection Panel" is "map driven".
>
> So I don't think we need the "highlight the feature in a different color".
>
> Thanks again!
> -Buddy Hu
>
> ________________________________________
>
> Hi Dave,
>
> Thanks for your reply!
> Your suggestion is valuable for me. It's ideal if we can highlight the
> features in different color.
> However, as I know, we can't support different highlight color with
> current API. Do you know whether we have this API to support the
> different highlight color?
>
> Thanks,
> -Buddy Hu
>
> -----Original Message-----
> From: [hidden email]
> [mailto:mapguide-internals- [hidden email]] On Behalf Of Dave
> Wilson
> Sent: Friday, August 21, 2009 10:18 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RFC 81 is ready for review
>
> I also think there should be a mechanism that allows the user to
> select a feature from the set and it's highlight color should be
> different. If there are 5 parcels selected the user can pick one from
> the tree and it is highlighted Red for example instead of blue so that
> it is easily distinguished from the others.
>
> Dave
>
> -----Original Message-----
> From: [hidden email]
> [mailto:mapguide-internals- [hidden email]] On Behalf Of
> Jackie Ng
> Sent: Friday, August 21, 2009 3:20 AM
> To: [hidden email]
> Subject: Re: [mapguide-internals] RFC 81 is ready for review
>
>
> I am a bit miffed that this RFC effectively invalidates most, if not
> all the work I've done so far on RFC71
>
> But having said that, this looks to be a superior solution, not to
> mention also that my real life priorities have changed somewhat, grinding my dev.
> work on RFC71 to a halt.
>
> - Jackie
>
>
> Buddy Hu wrote:
> >
> > Hi All,
> >
> > The RFC 81- Add a new widget Feature Inspector is ok for review.
> > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
> > Any comments will be appreciated.
> >
> > Thanks,
> > -Buddy Hu
> > _______________________________________________
> > mapguide-internals mailing list
> > [hidden email]
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/RFC-81-is-ready-for-
> review-tp3485127p3487404.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jason Birch

Re: RFC 81 is ready for review

Reply Threaded

In reply to this post by Traian Stanev

I see the value of this tool, but I would not be happy to see it replace a basic selection widget. It's too GIS/CAD, with far too many choices for a non-expert to figure out.

More to say, but have to go...

----- Original Message -----
From: [hidden email] <[hidden email]>
To: [hidden email] <[hidden email]>
Sent: Mon Aug 24 08:56:44 2009
Subject: RE: [mapguide-internals] RFC 81 is ready for review

There's no point in having redundant functionality. This RFC seems to cover
RFC 71 and more. I have no qualms about suspending/cancelling my work on RFC
71.

- Jackie

Buddy Hu wrote:

>
> Hi Kenneth, Thanks for your reply!
>
> About the overlap with RFC 71, I think we don't make any changes to the
> existing Selection Panel. If Jackie want to introduce the Selection Panel
> to the AJAX view, I am pleasure to see this happens. If not, I think the
> Feature Inspector panel will cover some functionalities of the Selection
> Panel.
>
> For the typo of "Inverse Selection", I will update it later. Thanks for
> your good catch.
>
> And I don't think we need any server or Webserver code changes for this
> RFC. I will clarify these in the "Implications" part.
>
> And I'm not intent to support the sort or filter for the properties now.
>
> For the Gzip, we get this suggestion from Paul Spencer. I didn't do any
> test for this yet. For more details, you can check the mail I attached.
>
> Thanks for your reply again! I will update my RFC and post it again.
>
> -Buddy
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Kenneth
> Skovhede, GEOGRAF A/S
> Sent: Friday, August 21, 2009 4:04 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] RFC 81 is ready for review
>
> This overlaps a bit with RFC 71:
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc71
>
> At least the tree for display in the AJAX viewer should be present
> there, and I belive Jackie has developed this already?
>
> There is a slight spelling error in the "Inverse selection" menu item.
>
> Are there any changes required in the server code, or is this done with
> the current selection system?
>
> There has been questions about the order of properties, some want them
> sorted, some want them as is, will there be an option to select sort
> modus?
>
> To use GZip compression, is it possible to just serve the .gz file or
> does it require a webserver change to supply the compression header?
> I seem to recal that some browsers do not support GZip compression, and
> the served file should obey the compression flag to ensure compatibility.
>
> If a webserver change is required, will the change include maintenance
> for the installer?
>
> The test plan should include testing with a range of browsers.
>
> I am overall positive, the preview looks cool, and the addition is
> sorely needed.
>
> Regards, Kenneth Skovhede, GEOGRAF A/S
>
>
>
> Buddy Hu skrev:
>> Hi All,
>>
>> The RFC 81- Add a new widget Feature Inspector is ok for review.
>> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
>> Any comments will be appreciated.
>>
>> Thanks,
>> -Buddy Hu
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>

--
View this message in context: http://n2.nabble.com/RFC-81-is-ready-for-review-tp3485127p3504295.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Dave Wilson

RE: RFC 81 is ready for review

Reply Threaded

Let me repost with some better clarification of points and concerns:

1) I had suggested based on preview requests that there be an additional highlight color so that users can select one of the features in the set and see this separate from the others. This would be done with an additional dynamic overlay. The proposed solution of checking and un-checking items in the tree to isolate a particular feature is less user friendly and requires more server rendering to redraw all the features minus any the user has unchecked. If the user could simply walk the tree using up/down arrows (or clicking a particlar node) and alternately redraw just the one feature they are on with an alternate highlight this would involve less processing. As well if there are many parent nodes with records underneath I think it's more of an awkward binary search disabling nodes/records trying to find just the one the user wants.

2) What restricts the number of features that can be selected and viewed using the Inspector? If a user is zoomed out and has selected 20,000 features can they use the Inspector? Is there a limit to prevent retrieving thousands of features and all their properties?

3) Are we going to return all the properties of each feature in the tree? If 20 or 30 features are enabled this won't fit into the tree in any readable form.

4) The RFC doesn't discuss how we got to this selection set. What if the selection is a result of a search or API request and multiple features are selected all over the map and aren't actually adjacent? What if not all the features are in view (in other words we didn't Zoom to Selection) Do we care? If we (or the programmer) didn't Zoom to Selection and all the features aren't visible at the current scale will we pan to the feature as the user interacts with them in the Inspector?

5) What if the selection set is a result of a search, but the layer isn't enabled at the current scale? Are there odd conditions where the selection set can include features whose layers aren't enabled in the legend or possibly their layer isn't enabled at this scale?

I get the impression the RFC is trying to handle a specific case where the user may have selected a small area in an effort to find a particular feature or at least uniquely identify the features in the selection set. I'm not sure it addresses how the selection set was actually created?

Regards,
Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Monday, August 24, 2009 10:41 AM
To: '[hidden email]'
Subject: Re: [mapguide-internals] RFC 81 is ready for review

I see the value of this tool, but I would not be happy to see it replace a basic selection widget. It's too GIS/CAD, with far too many choices for a non-expert to figure out.

More to say, but have to go...

----- Original Message -----
From: [hidden email] <[hidden email]>
To: [hidden email] <[hidden email]>
Sent: Mon Aug 24 08:56:44 2009
Subject: RE: [mapguide-internals] RFC 81 is ready for review

There's no point in having redundant functionality. This RFC seems to cover RFC 71 and more. I have no qualms about suspending/cancelling my work on RFC 71.

- Jackie

Buddy Hu wrote:

>
> Hi Kenneth, Thanks for your reply!
>
> About the overlap with RFC 71, I think we don't make any changes to
> the existing Selection Panel. If Jackie want to introduce the
> Selection Panel to the AJAX view, I am pleasure to see this happens.
> If not, I think the Feature Inspector panel will cover some
> functionalities of the Selection Panel.
>
> For the typo of "Inverse Selection", I will update it later. Thanks
> for your good catch.
>
> And I don't think we need any server or Webserver code changes for
> this RFC. I will clarify these in the "Implications" part.
>
> And I'm not intent to support the sort or filter for the properties now.
>
> For the Gzip, we get this suggestion from Paul Spencer. I didn't do
> any test for this yet. For more details, you can check the mail I attached.
>
> Thanks for your reply again! I will update my RFC and post it again.
>
> -Buddy
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Kenneth Skovhede, GEOGRAF A/S
> Sent: Friday, August 21, 2009 4:04 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] RFC 81 is ready for review
>
> This overlaps a bit with RFC 71:
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc71
>
> At least the tree for display in the AJAX viewer should be present
> there, and I belive Jackie has developed this already?
>
> There is a slight spelling error in the "Inverse selection" menu item.
>
> Are there any changes required in the server code, or is this done
> with the current selection system?
>
> There has been questions about the order of properties, some want them
> sorted, some want them as is, will there be an option to select sort
> modus?
>
> To use GZip compression, is it possible to just serve the .gz file or
> does it require a webserver change to supply the compression header?
> I seem to recal that some browsers do not support GZip compression,
> and the served file should obey the compression flag to ensure compatibility.
>
> If a webserver change is required, will the change include maintenance
> for the installer?
>
> The test plan should include testing with a range of browsers.
>
> I am overall positive, the preview looks cool, and the addition is
> sorely needed.
>
> Regards, Kenneth Skovhede, GEOGRAF A/S
>
>
>
> Buddy Hu skrev:
>> Hi All,
>>
>> The RFC 81- Add a new widget Feature Inspector is ok for review.
>> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81
>> Any comments will be appreciated.
>>
>> Thanks,
>> -Buddy Hu
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>

Tom Fukushima

RE: RFC 81 is ready for review

Reply Threaded

In reply to this post by Jackie Ng

Hi Jackie,

RFC 81 needs more details about the UI, use cases, limitations and implementation. I believe that it will be rewritten or withdrawn.

The UI (as I understand it) for RFC 81 is similar with RFC 71 in that it handles showing properties for multiple selections. But the feature inspector (RFC 81) is more for doing other types of analysis such as reselecting, or zooming to features. I think that the "feature inspector" is more for an advanced user, and the "Properties" widget will still be important. So I don't think that you should suspend or cancel the work on RFC 71.

Cheers
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Monday, August 24, 2009 9:57 AM
To: [hidden email]
Subject: RE: [mapguide-internals] RFC 81 is ready for review

There's no point in having redundant functionality. This RFC seems to cover
RFC 71 and more. I have no qualms about suspending/cancelling my work on RFC
71.

- Jackie

Buddy Hu wrote:

--
View this message in context: http://n2.nabble.com/RFC-81-is-ready-for-review-tp3485127p3504295.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Tom Fukushima

RFC 81 retracted

Reply Threaded

Hi All,

FYI, MapGuide RFC 81 "Add a new widget Feature Inspector" has been retracted.
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc81

Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Friday, August 28, 2009 1:50 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC 81 is ready for review

Hi Jackie,

RFC 81 needs more details about the UI, use cases, limitations and implementation. I believe that it will be rewritten or withdrawn.

The UI (as I understand it) for RFC 81 is similar with RFC 71 in that it handles showing properties for multiple selections. But the feature inspector (RFC 81) is more for doing other types of analysis such as reselecting, or zooming to features. I think that the "feature inspector" is more for an advanced user, and the "Properties" widget will still be important. So I don't think that you should suspend or cancel the work on RFC 71.

Cheers
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Monday, August 24, 2009 9:57 AM
To: [hidden email]
Subject: RE: [mapguide-internals] RFC 81 is ready for review

There's no point in having redundant functionality. This RFC seems to cover
RFC 71 and more. I have no qualms about suspending/cancelling my work on RFC
71.

- Jackie

Buddy Hu wrote:

--
View this message in context: http://n2.nabble.com/RFC-81-is-ready-for-review-tp3485127p3504295.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals