Contents:
Requirements
Summary of Changes in This Version
Limitations
Installation in a Windows PC
Usage
Custom Startup Menus
Client and Host Methods Supported
As of Version: 3.3.36 (Dec 15 2008)
Requirements
Jargon Reader for Windows can be run on the following operating systems:
- Windows 95
- Windows 98
- Windows 98SE
- Windows ME
- Windows NT
- Windows 2000
- Windows 2003
- Windows XP
- Windows Vista
Summary of Changes in This Version:
Limitations:
- 300 components per frame.
- maximum of 128 preference items ("ini" file parameters) per app.
- maximum of 10 levels of nested elements in XML files.
- 50 tables for all combined running apps (25 in versions 3.3.16 and older).
- http request (send) buffer of 120KB. (35KB in versions 3.3.10 and older)
- SSL receive buffer of 250KB.
- Maximum of 16 menu items that can be added to an app.
Installation in a Windows PC:
Automatic Installation via Microsoft Installer Program
- If zipped, unzip the MSI installer program (xxx.msi) on your PC .
- Run the setup program and accept all prompts.
Manual Installation via Windows Explorer
Usage
- Click on the shortcut to start Jargon Reader.
- To see an example of a ReaderWIN app, in the "Startup Page URL" field enter:
http://www.jargonsoft.com/V3/xml/util/dbwin.ini
- Click "Load".
- When the installed application listbox contains an entry named "dbwin"
select it and click "Run".
- This "dbwin" app is a simple database schema and data browser. This example
is connected to a copy of Progress Software's "Sports2000" demo database.
Custom Startup Menus
- At startup, Jargon Reader will:
- See if an "ini" file is specified on the command line. If so, load it and run that app.
- If not, see if there is an ApplicationMenu.dom (cache file) already in the cache folder
- If not, see if there is an external ApplicationMenu.xml in the same folder
as the "Start In" property of the shortcut to ReaderWIN (if a shortcut is used),
otherwise the folder where the actual ReaderWIN.exe is located.
- If not, use the hardcoded default ApplicationMenu.xml that is built into
Jargon Reader.
- The ApplicationMenu.xml procedure must specify where to get the "ini"
file for each of the apps that can be run from it. Often the ApplicationMenu.xml
is used as a login or "start" window and the only app it runs is a menu app.
The sample custom ApplicationMenu.xml provided with Jargon Writer has a
"baseURL" value that needs to be set to the web server folder where the ini
file is located (e.g. menu.ini). That ini file will have the normal 4 values
that allow Jargon Reader to then load and run the menu.xml (from the same
folder on the web server).
- See the xml/JargonDemo folder in your Jargon Writer release for an example of
how to populate the "baseURL" from a host procedure. It can also be hardcoded into
ApplicationMenu.xml if you wish.
Client and Host Methods Supported
For a complete list of the client methods and host methods that are currently
supported for use with this version of Jargon Reader, see the following
documents:
(end of readme file)
|