Autodesk 15606-011408-9330 User Guide - Page 40

Autodesk MapGuide Viewer API, Web Browser APIs, Stand-Alone Applications

Page 40 highlights

You can use these scripting languages to access the Autodesk MapGuide Viewer API and the Netscape and Internet Explorer browser APIs. The scripts can range from a single line to complex client-side map applications. For more information, see "Choosing a Viewer/Browser Environment," on page 63, and refer to the Autodesk MapGuide Viewer API Help. Autodesk MapGuide Viewer API Autodesk MapGuide Viewer exposes an object-oriented programming interface (API) that gives you programmatic access to Autodesk MapGuide Viewer functionality. For example, you can create a redlining application that gives users the ability to digitize features and add notations to a map. You can access the Autodesk MapGuide Viewer API from a browser script or from a stand-alone application you create that hosts the Viewer. The API is available when you install any version of Autodesk MapGuide Viewer. For more information, refer to the Autodesk MapGuide Viewer API Help. Web Browser APIs The Netscape and Internet Explorer APIs give you programmatic access to browser and document functionality. The APIs include a Document Object Model (DOM) that exposes the elements in an HTML page. With the browser APIs, you can write a script that creates a new window or frame and then outputs HTML to it dynamically. You can also create HTML pages that change dynamically on user interaction. (This is called Dynamic HTML.) Note The Document Object Models for Netscape and Internet Explorer vary somewhat. Therefore, when writing a single script for both browsers, be sure to test your script carefully in both browsers. Stand-Alone Applications You can write a stand-alone C++, Visual Basic, or Java application that hosts Autodesk MapGuide Viewer without a Web browser. For details about supported platforms, see "Choosing a Viewer/Browser Environment" on page 63. 40 | Chapter 2 Understanding Autodesk MapGuide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

40
|
Chapter 2
Understanding Autodesk MapGuide
You can use these scripting languages to access the Autodesk MapGuide
Viewer API and the Netscape and Internet Explorer browser APIs. The scripts
can range from a single line to complex client-side map applications. For
more information, see
Choosing a Viewer/Browser Environment,
on page
63, and refer to the
Autodesk MapGuide Viewer API Help
.
Autodesk MapGuide Viewer API
Autodesk MapGuide Viewer exposes an object-oriented programming inter-
face (API) that gives you programmatic access to Autodesk MapGuide Viewer
functionality. For example, you can create a redlining application that gives
users the ability to digitize features and add notations to a map.
You can access the Autodesk MapGuide Viewer API from a browser script or
from a stand-alone application you create that hosts the Viewer. The API is
available when you install any version of Autodesk MapGuide Viewer. For
more information, refer to the
Autodesk MapGuide Viewer API Help
.
Web Browser APIs
The Netscape and Internet Explorer APIs give you programmatic access to
browser and document functionality. The APIs include a Document Object
Model (DOM) that exposes the elements in an HTML page.
With the browser APIs, you can write a script that creates a new window or
frame and then outputs HTML to it dynamically. You can also create HTML
pages that change dynamically on user interaction. (This is called
Dynamic
HTML
.)
Note
The Document Object Models for Netscape and Internet Explorer vary
somewhat. Therefore, when writing a single script for both browsers, be sure to
test your script carefully in both browsers.
Stand-Alone Applications
You can write a stand-alone C++, Visual Basic, or Java application that hosts
Autodesk MapGuide Viewer without a Web browser. For details about
supported platforms, see
Choosing a Viewer/Browser Environment
on
page 63.