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

[Fischer, Brian]

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.

Brian Fischer
Houston Engineering, Inc.
Maple Grove, MN
(763) 493-4522


-----Original Message-----
From: Brent Fraser [mailto:bfraser at geoanalytic.com] 
Sent: Monday, February 23, 2009 4:23 PM
To: geomoose-users at lists.sourceforge.net
Subject: [Geomoose-users] Any plans to make View Extents a service?


I'm in the process of using GeoMoose as a client-side framework for
multiple users.  Each user would have a different INITIAL_VIEW,
Fullview, and Jump-To view extents.  It seems like these extents would
be good candidates for a "service" with the values returned being unique
to the particular user.

Any opinions or experiences on that?

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