[Geomoose-users] Any plans to make View Extents a service?

[Jim Klassen]

This is something I've been pondering for awhile, but not enough to get to any coding...

The magic feature that I want that would make things like this easier is allowing the services to configure themselves at runtime. I have a couple of services where what is search-able changes over time based on what is stored in a database. Thus, being able to pull the drop down lists from the DB (via a server side service) would be easier to maintain than fixed drop down lists in the mapbook (or config.js).

Very rough idea...
create a parameter in the mapbook to indicate that a service should try to auto-config, possibly with the url of a document to get that contains the necessary parameters... say XML or JSON.

When the user selects the service/tool/whatever, GeoMOOSE makes a quick AJAX/JSON call to the provided URL which responds with the options/questions to present to the user.

The user then makes the request as normal.

Example: User clicks Zoom to Extents. GeoMOOSE asks which user you would like extents for? The user responds and clicks submit and the extents for that user come up as the result of a search tool. (BTW: you can do this now if you write the server side service to implement the search and hard code the user list into the mapbook.)


(Even better would be if the drop downs and/or other fields could be linked and change depending on what others are set to.)

>>> Brent Fraser <bfraser at geoanalytic.com> 02/24/09 3:11 PM >>>
Brian,

  I'm trying to avoid the separate config files as there are about 100 users with 10 to 100 different areas each.  There's a database on the server with lots of other user-specific map and attribute info I'll be querying so I thought why not build an Extent service...

  I'll have a look in the 1.2 version.


Fischer, Brian wrote:
> The funny thing is we had this as a part of the xml mapbook, but we
> moved in into the config.js file in version 1.4 for performance reasons.
> When it was in the .xml file it caused the application to load slow when
> you have a big list of zoom to items.
> 
> Unfortunately I don't think there would be a way to configure GM 1.6 to
> do this without hacking a bunch of code.  The only way I can think of is
> to store a separate config.js file for each of your users.
> 
> I will throw out that in GM 2.0 we are planning on moving that back into
> the .xml file and Dan's vision is to only have one configuration file
> that is the XML map book.

That's got my vote (as long as there's not sacrifice in performance).

Thanks!

Brent Fraser


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geomoose-users