Autodesk 15606-011408-9320 User Guide - Page 38

Web Browser APIs, Stand-alone Applications, Server-Side Applications

Page 38 highlights

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 could write a script that creates a new window or frame and then outputs HTML to it dynamically. You could 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 59. Server-Side Applications Server-side applications run on the server (or host), creating or processing data and serving it to the client machine. A server-side application (also known as a server app) might be a counter that shows how many times a site has been visited, or it might be a database that builds and serves HTML pages dynamically. The Autodesk MapGuide LiteView Extension, used to display raster maps without a browser, is also an example of a server-side application. In Autodesk MapGuide, server-side applications are typically used to generate and serve reports or to allow map data on the server to be updated by a user from his or her browser. Please note that these applications are typically a combination of client-side and server-side applications, but for the sake of simplicity, they are discussed here as server-side applications. 38 | 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

38
|
Chapter 2
Understanding Autodesk MapGuide
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 could write a script that creates a new window or
frame and then outputs HTML to it dynamically. You could 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 59.
Server-Side Applications
Server-side applications run on the server (or
host
), creating or processing
data and serving it to the client machine. A server-side application (also
known as a
server app
) might be a counter that shows how many times a site
has been visited, or it might be a database that builds and serves HTML pages
dynamically. The Autodesk MapGuide LiteView Extension, used to display
raster maps without a browser, is also an example of a server-side application.
In Autodesk MapGuide, server-side applications are typically used to
generate and serve reports or to allow map data on the server to be updated
by a user from his or her browser. Please note that these applications are typi-
cally a combination of client-side and server-side applications, but for the
sake of simplicity, they are discussed here as server-side applications.