Autodesk 15606-011408-9330 User Guide - Page 39

Client-Side Application Components, HTML s

Page 39 highlights

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 HTML Pages Usually, a client-side application is an instance of Autodesk MapGuide Viewer that is displayed in an HTML page by means of the , , or tag. ( is used for the Netscape Plug-In, for the ActiveX Control, and for the Java Edition). The HTML page might contain form elements (such as buttons and list boxes) and code that access the Web browser API and the Autodesk MapGuide Viewer API. You can also display the map full-screen (not embedded in an HTML page) by using the tag in an HTML page and creating a link to the MWF. For more information, refer to the Autodesk MapGuide Viewer API Help. Web Browser Scripts Autodesk MapGuide supports the following HTML scripting languages:  JavaScript-JavaScript is a full-featured scripting language that supports the Netscape Plug-In on the Windows platform and the Java Edition on the Windows and Sun Solaris platforms.  JScript-JScript is Microsoft's variant of the JavaScript language. It sup- ports the ActiveX Control and Java Edition for Internet Explorer on Windows platforms. Throughout this book, we will often refer to JScript and JavaScript collectively as JavaScript.  VBScript-VBScript is a Visual Basic-derived language that supports the ActiveX Control for Internet Explorer on Windows platforms. Developing Applications with Autodesk MapGuide | 39

  • 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

Developing Applications with Autodesk MapGuide
|
39
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
HTML Pages
Usually, a client-side application is an instance of Autodesk MapGuide
Viewer that is displayed in an HTML page by means of the
<EMBED>
,
<OBJECT>
, or
<APPLET>
tag. (
<EMBED>
is used for the Netscape Plug-In,
<OBJECT>
for the ActiveX Control, and
<APPLET>
for the Java Edition). The
HTML page might contain form elements (such as buttons and list boxes)
and code that access the Web browser API and the Autodesk MapGuide
Viewer API. You can also display the map full-screen (not embedded in an
HTML page) by using the
<A HREF>
tag in an HTML page and creating a link
to the MWF. For more information, refer to the
Autodesk MapGuide Viewer API
Help
.
Web Browser Scripts
Autodesk MapGuide supports the following HTML scripting languages:
JavaScript
JavaScript is a full-featured scripting language that supports
the Netscape Plug-In on the Windows platform and the Java Edition on
the Windows and Sun Solaris platforms.
JScript
JScript is Microsoft
s variant of the JavaScript language. It sup-
ports the ActiveX Control and Java Edition for Internet Explorer on Win-
dows platforms. Throughout this book, we will often refer to JScript and
JavaScript collectively as JavaScript.
VBScript
VBScript is a Visual Basic-derived language that supports the
ActiveX Control for Internet Explorer on Windows platforms.