[mapguide-internals] MapGuide Comments

[Haris Kurtagic]

I look at Selection in a same way as other query parameters: center,
scale,...

Right now in viewer I implemented as settintg selection first and than
requesting image
I am thinking about redesign to send selection filter with every request
for image.

Haris

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason
Birch
Sent: Friday, September 14, 2007 5:11 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide Comments

Haris,

In your model, where would the selection state be stored?

Jason 

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: Thursday, September 13, 2007 13:19
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide Comments

First of all, thank you for sharing your thoughts.

I think client had to keep data about current Map view. For example if
you would like to Zoom in, client would recalculate new scale and send
it to server.
There is no server command for change scale by 1.5 ( and also that type
of "incremental" command would be inappropriate) and doing calls get
scale - recalculate - send back doesn't sound right.

I am now looking at Map as data, data with state ( existing data from
features, new data ).
View of Map (Image) I look as stateless.

When I am thinking about this than I try to draw parallel between
Map/Image and Table/Query in database. Map is a Table in database.
Generating image is similar to generating view on your table data by
sending parameters ( center ,scale ,layers on/off ,...).

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