With the eva/3 version 1.4 the new class
SApplet is introduced. With this class, eva/3 forms can be executed as a component of a web page
(s. fig. 14
).

Fig. 14: Eva/3 Application in a Web Page
The Applet should be embedded in the HTML code as follows:
... <applet width="640" height="480" code="com.odc.eva3.rt.se.form.SApplet.class" archive="anwendung.jar,eva3rt.jar" align="left" hspace="20" vspace="12"> <param name="-p" value="anwendung.jar"> <param name="-o" value="Formulare/Start.form"> </applet> ...
| width / height | With and height of the applet. Keep in mind that the application is executed inside of the defined rectangle |
| code | The SApplet class |
| archive | All .jar files used by the application |
| param name="-p" | The eva/3 ProjectPath. All used eva/3 projekt-archieves has to be specified, separated by ; |
| param name="-o" | The form, wich with the eva/3 application should start |
| param name="-f" | This optional defines the form that will be displayed
when the application calls the CloseActiveForm macro. The
application will continue executing, so it is task of the Form to decide what
should happen with the MenuBar. When the parameter is not defined, the eva/3 logo will be displayed |
On the webserver the eva/3 runtime and the eva/3 projects must be made available as .jar archives. They all must be signed with keytool and jarsigner. (see Running an eva/3 Application Builder application using Java Web start).
The WindowIconifiedMacro and the WindowDeiconifiedMacro are never called in an SApplet. The WindowActivatedMacro
and the WindowDeactivatedMacro are only called
once. When you develope your eva/3
application, keep in mind that the behavior of SApplets differs from the behavior of an eva/3 application
started with main() at this points.
When developing a database driven application, the used databases must be available for the users workplace.