[Chameleon] WMSBrowser: SRS

[Paul Spencer]

Bart,

bartvde at xs4all.nl wrote:

> Hi Paul,
> 
> great.
> 
> I have another question about the WMSBrowser widget.
> 
> Our customer wants a situation in which not every user of an application
> has rights on the Manage Servers widget. But all users should have access
> to the WMSBrowser widget in order to be able to add external layers to
> their application.
> 
> Is there an easy way to use a widget parameter to optionally include the
> "Manage Servers" into the WMSBrowser dialog?
> 

um ... there are two modes of operation, one where the widget modifies 
the actual cache, and one where the cache is copied to the users session 
and changes made by the user only persist for the session.

USEUSERSESSION=[true|false]

in the WMSBrowser widget tag.

We could also add a 'MANAGESERVERS=[true|false]' but the question would 
be how to control that on a user basis ... are the users coming from a 
portal?  If yes, then I see two choices:

1. two application templates chosen based on user, one which allows 
editing and one which doesn't

2. use template replacements as in:

USEUSERSESSION="[$bManageServers$]"

The value of [$bManageServers$] will be replaced with the value of 
bManageServers from the URL (get or post) request ...

(same could be done if we put in a 'manageservers=[true|false]'


> BTW: there is a small javascript error in mapbrowser_iframe_en.html:
> 
> if (obj.options[i].value == documents.forms[0].WMSSERVERS.value)
> 
> documents should be document (you won't notice it in Mozilla, but in IE it
> prevents the Manage Servers dialog from popping up).
> 

found that yesterday, fix in cvs :)

> Best regards,
> Bart
> 
> 
>>Bart,
>>
>>I'll look at adding an SRS parameter to the widget tag and I'll see if
>>the WMSCACHEDIRECTORY should be a mandatory attribute.
>>
>>Paul
>>
>>bartvde at xs4all.nl wrote:
>>
>>
>>>Hi list,
>>>
>>>I got the WMSBrowser widget to work (such a cool widget BTW), but I had
>>>some problems changing the SRS that the WMSBrowser widget uses.
>>>
>>>It uses by default lat/lon (EPSG:4326) even if your main Chameleon
>>>application is in a different SRS. It also uses the LatLonBoundingBox
>>>from
>>>the capabilities to determine the extents in the preview.
>>>
>>>Are there any plans to incorporate a SRS attribute into the WMSBrowser
>>>widget?
>>>
>>>I had to hardcode some changes to fit the Dutch RD system into the
>>>WMSBrowser widget.
>>>
>>>Oh, and don't forget to set the following attribute if you plan on using
>>>it (it took me some time to figure out why my list of servers was not in
>>>the widget):
>>>WMSCACHEDIRECTORY="/ms4w/apps/chameleon/data"
>>>
>>>Best regards,
>>>Bart
>>>_______________________________________________
>>>Chameleon mailing list
>>>Chameleon at lists.maptools.org
>>>http://lists.maptools.org/mailman/listinfo/chameleon
>>>
>>
>>--
>>  -----------------------------------------------------------------
>>|Paul Spencer                           pspencer at dmsolutions.ca   |
>>|-----------------------------------------------------------------|
>>|Applications & Software Development                              |
>>|DM Solutions Group Inc                 http://www.dmsolutions.ca/|
>>  -----------------------------------------------------------------
>>
>>_______________________________________________
>>Chameleon mailing list
>>Chameleon at lists.maptools.org
>>http://lists.maptools.org/mailman/listinfo/chameleon
>>
> 
> 
> _______________________________________________
> Chameleon mailing list
> Chameleon at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/chameleon
> 

-- 
  -----------------------------------------------------------------
|Paul Spencer                           pspencer at dmsolutions.ca   |
|-----------------------------------------------------------------|
|Applications & Software Development                              |
|DM Solutions Group Inc                 http://www.dmsolutions.ca/|
  -----------------------------------------------------------------