Autodesk 15606-011408-9320 User Guide - Page 61

Choosing a Viewer/Browser Environment, ActiveX Control for Internet Explorer, Netscape Plug-In

Page 61 highlights

Components for Choosing a Viewer/Browser Environment (continued) Operating System Browser Viewer Language Solaris Netscape Navigator Java edition HTML, JavaScript, Java Any browser that supports PNG file format LiteView Extension ColdFusion (CF), Active Server Pages (ASP), Java Server Pages (JSP) or Perl none Java edition Java (stand-alone application) ActiveX Control for Internet Explorer The ActiveX Control works only within the Internet Explorer 4.01 and later browser for Windows. It exposes an API that is accessible from VBScript, JScript (Microsoft's implementation of JavaScript), and Java. The ActiveX Control API is exposed through ActiveX/COM/Automation technology. If you develop an application only for the ActiveX Control version of the Viewer, users can access that application with Internet Explorer only; if someone tries to view your application with Netscape, it will fail. You can also write stand-alone applications for the ActiveX Control with Visual Basic or C++. In this case, no browser is required, as your stand-alone application takes the place of a browser. Netscape Plug-In The Plug-In version of the Viewer works within Netscape Navigator 4.5 and later for Windows. It exposes an API that is accessible from JavaScript and Java. The Plug-In Viewer API objects are exposed via Netscape LiveConnect technology. If you develop an application only for the Plug-In version of the Viewer, users can access that application with Netscape only; if someone tries to view your application with Internet Explorer, it will fail. Choosing a Viewer/Browser Environment | 61

  • 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

Choosing a Viewer/Browser Environment
|
61
ActiveX Control for Internet Explorer
The ActiveX Control works only within the Internet Explorer 4.01 and later
browser for Windows. It exposes an API that is accessible from VBScript,
JScript (Microsoft
s implementation of JavaScript), and Java. The ActiveX
Control API is exposed through ActiveX/COM/Automation technology. If
you develop an application
only
for the ActiveX Control version of the
Viewer, users can access that application with Internet Explorer only; if
someone tries to view your application with Netscape, it will fail. You can
also write stand-alone applications for the ActiveX Control with Visual Basic
or C++. In this case, no browser is required, as your stand-alone application
takes the place of a browser.
Netscape Plug-In
The Plug-In version of the Viewer works within Netscape Navigator 4.5 and
later for Windows. It exposes an API that is accessible from JavaScript and
Java. The Plug-In Viewer API objects are exposed via Netscape LiveConnect
technology.
If you develop an application
only
for the Plug-In version of the Viewer, users
can access that application with Netscape only; if someone tries to view your
application with Internet Explorer, it will fail.
Solaris
Netscape
Navigator
Java edition
HTML, JavaScript,
Java
Any browser that
supports PNG file
format
LiteView Extension
ColdFusion (CF),
Active Server
Pages (ASP), Java
Server Pages (JSP)
or Perl
none
(stand-alone
application)
Java edition
Java
Components for Choosing a Viewer/Browser Environment (
continued
)
Operating
System
Browser
Viewer
Language