Documentation specific to the Classic Macintosh version of Joker.

1.0	WHAT "MACINTOSH VERSION"?
	Joker has been written on a Macintosh in ANSI C++. The "ANSI" part means that,
	in theory, it should only require recompiling Joker on another computer system
	with an ANSI-compliant compiler for that platform to generate a perfectly
	working version of Joker for another platform.
	
	Note that I said "in theory". In practice, the ANSI standard's specifications
	are rather vague and are thus interpreted differently by every company that
	writes a compiler. Thus, ANSI code still needs to be adapted to other
	operating systems and needs to be tested thoroughly. Also, ANSI does not
	provide any routines that handle network access or graphical user interfaces.
	This is the reason why there is so far only a Macintosh version of Joker.
	
	However, to account for a port to Unix or Windows or another OS at a later
	time, I have chosen to strictly separate the platform-specific and the
	ANSI parts of Joker. This includes that I created a compatibility layer
	that is a very simple Mac application that listens for Apple Events and
	dispatches them to Joker's main entry point.
	
2.0	COMMAND LINE OPTIONS
	Joker's main entry point is like that of a DOS or Unix application, in
	that it works like a command. It takes a few parameters and allows you to
	specify some options on the command line prompt. But since the Mac has no
	command line, I had to choose a different approach:
	
	If you open Joker with ResEdit, you will find a 'CST#' resource named
	"Compiler Flags". This resource contains one entry each for the parameters
	to pass to Joker on startup, and Joker will read any strings you specify
	from this resource and pass them to the main entry point.
	
	Thus, whenever you see mention of a command line option or flag in the
	generic documentation, this means that you have to edit the 'CST#' resource
	to modify them.

3.0	HOW APPLE EVENTS WORK
	To let you handle any Apple Event the MacOS might send to Joker, Joker can
	not require you to provide the name of a script to run for each Apple Event.
	Instead, it will simply look for a text file named "cgi.txt" and will run
	any appleEvent message handler it finds in there (if you don't know how that
	handler is supposed to work, have a look at any HyperCard or SuperCard
	documentation you may find). If that handler does not exist or is passed,
	Joker will try to handle it itself (which, for an open application or open
	document Apple Event means to ask you for a script file to run or to run
	the specified file), or simply tell the OS it doesn't know what the hell
	it is supposed to do with this junk.
	
	This means that you can drop a text file onto Joker's icon to run it.
	Forget about all that command-line stuff the main documentation file tells
	you of.
	
	
(c) Copyright 2001 by M. Uli Kusterer, all rights reserved.