Release Notes 2.5.23

Weave 2.5.23 includes a number of bug fixes and enhancements. This release is predominately focused on enhancements to existing tools rather than the addition of new tools and functions. These enhancements have increased the flexibility and usability of some of Weave's standard tools. A full list of changes can be found at the Weave What's New page. 

Main enhancements in Weave 2.5.23 are:

 Spatial Identify

The Spatial Identify tool can be set to return result for all entities or only the entities associated with visible layers using the useVisibleEntities tag. 

For example, using this in your client XML file:

<item action="com.cohga.html.client.map.spatialIdentify">
        <useVisibleEntities>true</useVisibleEntities>
</item>

means that the ToC controls the layers that will be interrogated when using the Spatial Identify tool (i.e. the entities associated with visible layers will be used).

Conversely, setting the useVisibleEntities tag to false means that the Spatial Identify tool will return results for any entity (independent of whether the layer is visible or not). 

 Editing

• Spatial Editing
  • The createNew action will turn on the layer associated with the entity (if one is set) when the button is pressed. 
    
    
• Non-spatial Editing

• Support has been added for field groups so client input forms, built via <parameter> config items, can now group fields. This improves presentation of the input form. For example the following editor configuration:

  <editor:table id="nse.property_document"> 
  	<label>Property_document</label>
  	<datasource>gis</datasource>
  	<table>docs.property_document</table>
  	<parameter id="pid" label="PID" column="pid" dataType="integer" />
  	<parameter id="id" label="Id" column="id" dataType="integer" autogenerated="true" hidden="true"/>
  	<parameter id="details" label="Document Details">
  		<parameter id="url" label="URL" column="url"/>
  		<parameter id="description" label="Description" column="description" allowBlank="false"/>
  	</parameter>
  </editor:table>

  will produce this input form:
  
  
  

 Buffer Tool

• Buffer style enhancement
  
  • The buffer style can be set in the map view by added a <buffer> section in the <highlight> tags.

• Map highlight enhancement

  • It's now possible to specify that highlights and buffers are automatically removed from the map after a fixed delay, rather than waiting until the new map redraw using the <autoClear> and <autoClearDelay> tags.

Both of these enhancement are shown in the extract of the client XML file shown below:

<view id="com.cohga.html.client.map.mapView">
	....
	<highlight>
		<marker>
			....
		</marker>
		<vector>
			....
		</vector>
		<buffer>
			<strokeWidth>3</strokeWidth>
			<strokeColor>red</strokeColor>
			<strokeOpacity>0.75</strokeOpacity>
			<fillColor>yellow</fillColor>
			<fillOpacity>0.125</fillOpacity>
		</buffer>
		<autoClear>true</autoClear>
		<autoClearDelay>2000</autoClearDelay>
	</highlight>
	...
</view>

• Generation parameters
  • Various buffer related tools can now be configured to specify buffer generation parameters (include CRS to generate buffer in)

 Reports

• Report panel enhancement
  • Groups will expand and collapse based on the Active Entity to show all the reports available for that entity. 
• Improved BIRT legends
  • Legends have been neatened in BIRT reports that are using ArcGIS Server, WMS and Weave Map Engines. The improvements include better line wrapping for long text and the removal of redundant information. 

 Custom Stylesheets

• Support for custom stylesheets
  • It is now possible to create a CSS file that allows for simple overriding of CSS styles used in Weave.

  • For example a CSS file can be created to override the highlighting used in a Quick Search. The file needs be called ...\weave\platform\workspace\styles.css for it to be added to the client at startup. An example of its content is shown below:
    
    

.index-item .index-hl {
    background: #ffff00;
}

And it will produce this result in your Weave client:

• Note that for this to work the highlight tag needs to be set to "true" for the index combo in the client XML file (weave.indexcombo).