Autodesk 15606-011408-9320 User Guide - Page 36

Client-Side Application Components

Page 36 highlights

Example of an Autodesk MapGuide application Autodesk MapGuide applications can be client-side or server-side. A client-side application runs in the user's browser, using the processing power of the user's (client) computer. It is typically an HTML page that hosts Autodesk MapGuide Viewer and contains code to access the objects of the Autodesk MapGuide Viewer API. A server-side application runs on the server, and is typically used for generating custom map reports, generating dynamic HTML pages, and updating map resources such as databases, GIS, or CAD files. In most cases, applications are a combination of both client-side and server-side applications, but for the sake of simplicity, the following sections discuss the components as being one or the other. Client-Side Application Components Client-side applications run in the user's browser. A client-side application is usually made up of the following components:  A web browser and an HTML page that hosts Autodesk MapGuide Viewer  An MWF that is read by Autodesk MapGuide Viewer and displayed as a map  Web browser scripts that access the APIs for the browser and Autodesk MapGuide Viewer 36 | 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

36
|
Chapter 2
Understanding Autodesk MapGuide
Example of an Autodesk MapGuide application
Autodesk MapGuide applications can be
client-side
or
server-side
. A client-side
application runs in the user
s browser, using the processing power of the
user
s (client) computer. It is typically an HTML page that hosts Autodesk
MapGuide Viewer and contains code to access the objects of the Autodesk
MapGuide Viewer API. A server-side application runs on the server, and is
typically used for generating custom map reports, generating dynamic HTML
pages, and updating map resources such as databases, GIS, or CAD files. In
most cases, applications are a combination of both client-side and server-side
applications, but for the sake of simplicity, the following sections discuss the
components as being one or the other.
Client-Side Application Components
Client-side applications run in the user
s browser. A client-side application is
usually made up of the following components:
A web browser and an HTML page that hosts Autodesk MapGuide Viewer
An MWF that is read by Autodesk MapGuide Viewer and displayed as a
map
Web browser scripts that access the APIs for the browser and Autodesk
MapGuide Viewer