|
1
|
<h2>Other models</h2>
|
|
2
|
|
|
3
|
|
|
4
|
<p>
|
|
5
|
A Web Map Context document is just one type of model supported.
|
|
6
|
The configuration for this page demonstrates the mapbuilder
|
|
7
|
implementation for Context Collections.
|
|
8
|
This is an XML document which contains a list of context document URLs and a title.
|
|
9
|
</p>
|
|
10
|
|
|
11
|
<div id="collectionList"></div>
|
|
12
|
|
|
13
|
<table width="100%">
|
|
14
|
<tr>
|
|
15
|
<td id="mainButtonBar" align="left" valign="top" width="18"/>
|
|
16
|
<td id="mainMapPane"/>
|
|
17
|
</tr>
|
|
18
|
</table>
|
|
19
|
|
|
20
|
<p>
|
|
21
|
The widget for a context Collection is a text listing of the map titles
|
|
22
|
to be selected and is also generated by an XSL stylesheet.
|
|
23
|
Other widgets could defined to support a dynamic menu system for example.
|
|
24
|
</p>
|
|
25
|
|
|
26
|
<p>
|
|
27
|
In this case, the tools of the model are simply HTML links which execute
|
|
28
|
a JavaScript method. Note how the context model is set as the target of the
|
|
29
|
action using the <tagetModelId> property in the CollectionList widget.
|
|
30
|
The links call the JavaScript config[targetModelId].loadModel(modelUrl) method.
|
|
31
|
</p>
|
|
32
|
|
|
33
|
<p>
|
|
34
|
The MVC design pattern allows other document types to be supported very easily.
|
|
35
|
Please see the mapbuilder-lib Software Design Description
|
|
36
|
for details on how to extend the code base.
|
|
37
|
This is an open source project so contributions from other developers are encouraged.
|
|
38
|
</p>
|
|
39
|
|
|
40
|
<p align="right"><a href="?page=samples/tutorial3">previous</a></p>
|