Database config - widgets - WMSLayerAdder

[adube]

Add support for the WMSLayerAdder widget in the new config.

[adube]

r855, featuring :

• <layers> option no longer mandatory (you had to left if empty before)

• curl mode removed (wasn't complete anyway)

• new method of creating org_geoprisma_proxy_WidgetProxy objects in factory with the use of :
  • osmservice=blank
  • osmprocess=methodNameInWidgetPhpFile
  • osmwidgettype=widgettype (like 'wmslayeradder' for example)

• wmslayeradder now supported in db config. 'layers' option value must be defined in JSON. It was added to the sample (.sql adjusted).

• i18n files updated with

---

There are remaining things to be fixed or done :

• adjust wmslayeradder documentation

• create a documentation page or topic about the new way of creating a WidgetProxy with the new parameters (should be 'dev' stuff).

• in wmslayeradder.php, the curlCall method should check the url content before appending the rest of the request string. It should check for a '?' and if it's not there, add it. Right now, the following doesn't work (it should) : ​http://dev4g.mapgears.com/cgi-bin/mswms_gmap but this one does : ​http://dev4g.mapgears.com/cgi-bin/mswms_gmap?foo=bar

• when clicking on the 'External' tab, a js error occurs : this.data is undefined

• while testing with the above url, if a layer is added, a js error occurs : WMSLayerAdder.js line 248.

• icon images have broken links in the widget

[adube]

We don't know yet what is the plan for this widget, so I'll mark it for 1.0 since it's currently used in production and would be needed if we decide to keep it.

[adube]

This widget wasn't reviewed yet, so its fate will be decided in 1.2.

[adube]

Still need a review. Until then, pushed to 1.4.

[adube]

No review, pushed to 1.6.

[adube]

The WMSLayerAdder was deprecated in 1.6. I'm closing this as "WONTFIX".