[Geomoose-users] GeoMoose 2.0 Re: GeoMOOSE 2.0 Planning - Themenu bar

[Jim Klassen]

Keep in mind that you could also write a short script on the webserver to assemble multiple files into a mapbook which would give the same functionality as XML includes.

(And if you are worried about speed, you would keep the fully assembled files on the server for GeoMOOSE to access and have the script update the assembled files from the source XML files only after you change the source files.)

BTW: did you ever get my reply on USNG?

Jim K

>>> Dan Little <danlittle at yahoo.com> 10/10/08 4:01 PM >>>
There are ways to do includes, the problem with XML includes is that they are not universally supported by all of the Javascript-engines (as they are different between IE-versions, FF-versions, Opera, and Safari) and they also cause MASSIVE loading slow-downs as they require multiple AJAX requests and then doing document-node importing which is inherently a very slow process.


----- Original Message ----
> From: Mark Volz <MarkVolz at co.lyon.mn.us>
> To: geomoose-users at lists.sourceforge.net
> Sent: Friday, October 10, 2008 3:44:10 PM
> Subject: Re: [Geomoose-users] GeoMoose 2.0 Re: GeoMOOSE 2.0 Planning - The menu bar
> 
> Dan,
> 
> I think that we should move the menu items to the mapbook.  Is it possible to
> have an include statement in the mapbook xml?  That way users could define
> the menu locally in a mapbook, or if preferred globally via the include
> statement.  I also like Nelson's idea of having a way to disable the menu.  
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 9 Oct 2008 10:31:13 -0700 (PDT)
> From: Dan Little 
> Subject: [Geomoose-users] GeoMOOSE 2.0 Planning - The menu bar.
> To: GeoMOOSE Users List 
> Message-ID: <279438.96676.qm at web51409.mail.re2.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
> 
> Hey Everyone,
> 
> I'm working on GeoMOOSE 2 and I'm trying to mull over the menu bar.  If I had
> my way it would be gone, but I think I've seen enough people using it to
> where I don't want to do that. :-)
> 
> I am, however, thinking about integrating the Menu definition into the
> Mapbook for mapbook version 2.0.  This would have a few advantages:
> 1) Decrease the number of files needed to be downloaded at start-up
> 2) Decrease the amount of XML that needs to be parsed.
> 3) Decrease the amount of bugs in IE and Opera, where the multithreaded AJAX
> support is buggy despite all claims otherwise.
> 4) Defining the menu bar would be come consistent with the new way of
> defining the tool bar.
> 
> There's only one disadvantage as I see it, you could forseeably have
> installations that all use the same menu bar, but different mapbooks and not
> wish to change individual mapbooks if one is making a global change to the
> menubar.
> 
> I'd love to hear some feed back on this. 
> 
> Thanks,
> 
> -Duck
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geomoose-users



      

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geomoose-users