[mapguide-internals] RFC 81 is ready for review

Tue Aug 25 14:57:31 EDT 2009

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: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, August 24, 2009 10:41 AM
To: 'mapguide-internals at lists.osgeo.org'
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: mapguide-internals-bounces at lists.osgeo.org <mapguide-internals-bounces at lists.osgeo.org>
To: mapguide-internals at lists.osgeo.org <mapguide-internals at lists.osgeo.org>
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: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at 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 at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>   
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> 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
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals