An email discussion of this problem:

Bart,

the WMSBrowser is problematic because it is actually a standalone chameleon
application as well as a widget.  Or it was written as a standalone application,
I should say, then converted to a widget.  This makes it difficult to refer to
the popupcss in the app template because it is a template.

What needs to be done is:

1. remove static references to css and replace with [$PopupCSS$]
2. add $oApp->setVar( 'PopupCSS', $_SESSION['PopupCSS'] ); in the WMSBrowser.php
just before $oApp->CWCExecute();
3. replace static images with <CWC2 Type="Link" linktype="javascript"
jsfunction=" ... " .... > ... </cwc2> to create correct buttons

The complication here is that the WMSBrowser application page would need its own
sharedresource for styling the link widgets, which may or may not coincide with
the app developers main page's sharedresources (documentation issue I guess).

Anyway, it can be done and should be done   I'll try to get to it.

Paul

> Hi list,
>
> I have noticed the WMSBrowser widget is the only widget (AFAIK) which uses
> its own css file. This makes it difficult to have several Chameleon
> applications which use different colors. For this one would use the
> PopupCSS shared resource normally, but the WMSBrowser widget does not use
> this popup.css.
>
> Are there any specific reasons for this structure? Ofcourse the WMSBrowser
> widget is a specific widget because it is a Chameleon application by
> itself. Would it theoretically be possible in the current Chameleon
> structure to pass the value of the PopupCSS shared resource to the
> WMSBrowser widget?
>
> Another question, would it (theoretically) be possibly to use makeButton
> functions in the WMSBrowser instead of the static images?