Jargon Reader® for Windows README File

Contents:

Requirements

• Windows 95
• Windows 98
• Windows 98SE
• Windows ME
• Windows NT
• Windows 2000
• Windows 2003
• Windows XP

Summary of Changes in This Version:

• System Timer Methods New sys methods to run callback function when a timer fires
  
• Support for Fixed Fonts New methods to specify and apply fonts to text components
  
• Support for Mag Card Readers New serial callback method runs when specified string is received
  
• New Infrared Object/Methods New "irda" object and methods for using Infrared port
  
• Expanded Serial Port Support Support for all serial "COM" ports in serial port open method
  
• Copy/Delete/Rename/Move Files New "jsifile" methods to copy/delete/move/rename files
  
• Component Resizing Implemented horiz/vert fill on all components
  
• Starting Folder for Open/Save Specify starting folder for GetOpenFileName etc.(Windows only)
  

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.
  
• 25 tables for all combined running apps.
  
• SSL receive buffer of 250KB.
  
• Maximum of 16 menu items that can be added to an app.
  

Installation in a Windows PC:

• Select an installation folder and create it if it does not already exist. A suggested default install folder is: "C:\Jargonsoft\ReaderWIN".


• Extract the ".exe" file from the installation zip file. These zip files are named in the format "ReaderXXX9999.zip" where XXX is the platform abbreviation and 9999 is the version number (example: ReaderWIN3247.zip).
  Platform abbreviations for Windows include:
  WIN - Windows 32-bit Operating Systems
  PDA - Jargon PDA Emulator for Windows PC


• Copy the .exe file to the selected install folder.


• Right-click the .exe file and select Send To-->Desktop (Create Shortcut).


• Note that the first time the Reader executable is run, it will create a folder named "cache" in the same folder where the exe is located. This cache folder contains ".dom" files for each app that allow for quicker startup and that retain each app's "state" information (such as component contents).


• To automatically load and run a specified app, right-click the shortcut and select Properties. Modify the "Target" startup command by adding a local pathname or remote URL that specifies a ".ini" file, after the .exe filename. This works with both ReaderWIN and ReaderPDA.

  Here are several examples of different ways to do this:
  
  C:\Jargonsoft\ReaderWIN\ReaderWIN.exe http://www.jargonsoft.com/v3/xml/demo32/menu.ini
  
  C:\Jargonsoft\ReaderWIN\ReaderWIN.exe C:\Jargonsoft\xml\demo32\menu.ini
  
  C:\Jargonsoft\ReaderWIN\ReaderWIN.exe ../xml/demo32/menu.ini
  

Usage

1. Click on the shortcut to start Jargon Reader.
2. To see an example of a ReaderWIN app, in the "Startup Page URL" field enter:
   http://www.jargonsoft.com/V3/xml/util/dbwin.ini
3. Click "Load".
4. When the installed application listbox contains an entry named "dbwin" select it and click "Run".
5. 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

1. 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 Reader .exe file.
   • If not, use the hardcoded default ApplicationMenu.xml that is built into Jargon Reader.

2. 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).

3. 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

• Client Methods
• Host Methods for Java
• Host Functions for Microsoft ASP
• Host Procedures for Oracle PL/SQL
• Host Methods for Progress 4GL

Return to Version 3 Documentation Index