[Geomoose-users] GeoMoose core changes?

Sat Sep 22 12:46:04 PDT 2012

I meant to reply to the list.

Begin forwarded message:

> From: Jim Klassen <klassen.js at gmail.com>
> Date: September 21, 2012 23:30:25 CDT
> To: Brian Fischer <bfischer at houstoneng.com>
> Subject: Re: [Geomoose-users] GeoMoose core changes?
> 
> Brian,
> 
> Thanks for the feedback.
> 
> My intent is for the visible layers to be built as an extension.  However, to do this without breaking the rules, I need some changes in the core that expose more functionality to extensions.  The changes I need shouldn't impact existing use of the application. Alternatively, it might make some sense for it to end up in core because of all the bits it needs to hook into.  In either case there is nothing that would require anyone to use/enable it.
> 
> I don't expect it will be applicable to many sites since defining what should be in visible layers (remembering it reflects the stacked z-order as rendered) becomes very ugly if you are using the feature that allows one catalog layer to be linked to multiple map-source layer (that helps with label stacking) as one catalog layer may need to be in 2 or more places.  This is because it has to operate at the map-source level rather than the catalog layer level as this is ultimately what become OpenLayers layers.  Obviously, such behavior could be very confusing to end users with some mapbooks.
> 
> Not to confuse things too much, because I think the Visible Layers tab can be useful separate from the CSW catalog, but in my current use case I could almost see the existing catalog tab as what would be hidden.  As is, we are keeping it for now to hold the basemap type layers as the bulk (potentially 1000's) of the layers are available from the searchable CSW catalog.
> 
> Jim
> 
> On Sep 21, 2012, at 22:21, Brian Fischer <bfischer at houstoneng.com> wrote:
> 
>> HI Jim,
>> In general these things seem like really nice enhancements to the core.  The only things that I was not clear on is if you are proposing the Visible Layers tab be in core and the default way GeoMoose would work or if that would be the extension?  I personally am not a big fan of 2 tabs with layers in it as I think it is awkward for a user to have to switch back and forth all the time.  Would these enhancements work on the layers/map-sources in the main TOC tab as well?  Like ability to turn on/off layers.  Obviously the Up/Down Z-Order stuff would be difficult with groups and nested groups.
>> 
>> One idea is instead of another tab maybe you could put the visible layers in a  dojo widget such as a popup dialog that allows users to move layers up and down.  Just a thought as another way to get the same functionality but without the 2 tabs.
>> 
>> All and all good ideas, just need to clarify the visible tab is in core or an extension.
>> 
>> Brian Fischer, CFM
>> Principal | GIS Project Manager 
>> Houston Engineering, Inc.
>> O 763.493.4522 | D 763.493.6664 | M 763.229.2734
>> 
>> 
>> -----Original Message-----
>> From: geomoose-users-bounces at lists.osgeo.org [mailto:geomoose-users-bounces at lists.osgeo.org] On Behalf Of Jim Klassen
>> Sent: Friday, September 21, 2012 5:19 PM
>> To: geomoose-users at lists.osgeo.org List
>> Subject: [Geomoose-users] GeoMoose core changes?
>> 
>> I am working on Add (WMS) to Map from my CSW Catalog extension and a Visible Layers extensions and I found I need to make some changes to core code.  
>> 
>> Taking one step back... I need a way from my CSW catalog to add new layers (map-sources) to the map at runtime.  I also need a way to control these layers once they are added.  I have decided that it makes more sense to create a visible layers tab (like was in GeoMoose 1.x) that can handle these dynamic layers as well as provide a more intuitive interface for the Up/Down Z-Order problem introduced in 2.x.  (For my purposes a layer == a map-source for now, although the nesting of the layers within the map-sources could potentially be added later).
>> 
>> To do this I need a way to add a map-source at runtime and a way to hook into the events such that I can update my Visible Layers tab when something changes (from the regular catalog or from the CSW catalog).  I also need to be able to trigger events from the Visible Layers tab (such as move up/down/turn layer off) etc.  I think the event framework is (mostly) in place already.  Also, adding a layer on the fly directly to the OpenLayers map object works, but then it isn't part of what GeoMoose knows about (for instance GeoMoose.setVisibility would fail because it doesn't have a "path").
>> 
>> At a minimum it looks like I need to change some stuff around in Application.js
>> 
>> For starters I have split configureMapSources into it's outer loop and an inner function that actually creates the map-source.  I need this so I can call the later directly from my extensions.
>> 
>> At this point I am looking for thoughts/ideas on how to best not mess things up.
>> 
>> Jim
>> _______________________________________________
>> Geomoose-users mailing list
>> Geomoose-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/geomoose-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120922/a18ecc6b/attachment.html>