Containers for HTML query results

[yvesm]

Some GetFeatureInfo results are returned as complex HTML documents with hyperlinks. Our current default resultextgrid widget that holds query results cannot accomodate for such rich text. An example are query results for the OneGeology layer at http://geoprisma.org/samples/onegeology/default/index.php.

We need to define another queryresult container for rich HTML text.

Note : integrate getFeatureInfoURL and getFeatureInfoSRS (MapGears)

[yvesm]

The typical case will be that many layers will return parseable text (e.g. GML) that is amenable to store in an Ext grid as things are now but some layers will return HTML. So this means that some resources will need a container (e.g. a popup) other than the standard resultextgrid that will need to be triggered at the same time the resultextgrid is being populated by the query.

[adube]

This could be accomplished the same way as the "version" service option, see in #88. We could have a "info_format" service option that could be used by the queryonclick widget when making its query string.

Instead of loading the query and get the features from the callback method, we only need to put the url directly in the result panel (or push it among the available results). It would be nice to avoid having to define these new "html" panel holders inside the config (inside the resultextgrid widget). We already have the resource 'title' and that's the only thing needed for the tab label.

More to come.

[adube]

r876 and r877, featuring :

• new 'info_format' service option

• if service option 'info_format' is set to 'text/html', the queryonclick widget will use it

• queryresults now supporting 'info_format' 'text/html' as well. You don't need to setup anything inside the widget, but you still need to link it to the resource (as usual). The 'title' used in the 'tab' results uses the resource 'title' first. If not defined, it uses the 'name'.

• onegeology sample updated with the above changes, see ​here. It shows the queryonclick and resultextgrid widget now supporting the 'info_format' service option equal to 'text/html'. They can get along with the old method too.

• documentation added about the new option, see ​here

Also featuring (out of this widget topic but mentioned for record) :

• new 'getRequestParams' method for Proxy class. The 'onegeology' WMS service didn't accept to have parameters such as &osmresource[0]=xxx, neither &osmresource[]=xxx but &osmresource=xxx would have worked. Instead of using all parameters inside $_GET, only those that don't start with 'osm' should be used. That's what this method is used for : to get all original request parameters ( removing any starting with 'osm' ).

• the XMLConfig driver now supports the optional <title> tag defined inside a resource (in the config.xml)