home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Education
/
collectionofeducationcarat1997.iso
/
COMPUSCI
/
ORPH165A.ZIP
/
WHATS.NEW
< prev
Wrap
Text File
|
1993-12-10
|
13KB
|
226 lines
Orpheus v1.65
[December 9, 1993: I am currently hard at work on version 2.0 of
Orpheus, which is scheduled for release in the first quarter of 1994.
I'm excited by the features going into Orpheus 2.0, and by how well
the work is going. For a brief discussion of what you can look forward
to, please see the end of this file.]
Version 1.65 (October 12, 1993)
NEW FEATURES:
- Online help in the authoring program (OH.EXE) now includes the entire
command reference to the script language. In any programmable card,
place the cursor on a command and press F1 for the *complete*
reference to that command! Help in OH.EXE now has a full-screen
window for maximum usability. As a further improvement, Help in both
OH.EXE and the Reader follows the Reader's standard for hypertext
navigation: to retrace your steps, press the left arrow or click the
right mouse button.
FIXES:
- In the Reader, the hide() command was disabled. Fixed.
- In OH.EXE, if you edited an index entry and only changed the case
of one or more letters, the change was ignored. Fixed.
- In OH.EXE, if you attempted a block move to a location in the same
card where there was not enough room, your data would be lost. Now
the card is restored to its condition when last saved, assuring the
safety of your hypertext links.
OTHER CHANGES:
- Due to internal changes in the help file format, earlier versions of
the .HLP files are no longer compatible. This applies to both OH.EXE
and the Orpheus Reader.
- FileView in both programs behaves more intuitively when you're paging
down near the end of a file: if the last PgDn would normally show a
partial page, that's what you'll see. (This change is primarily for
the convenience of authors using FileView to import text.)
OTHER NOTES:
- December 9, 1993: A few weeks after releasing this version I found a
couple of bugs in OH.EXE's Index dialog. If you delete one or more
topics, or edit an existing topic, you may corrupt the index or even
crash the system. These are corrected in the code for Orpheus 2.00,
which is discussed at the end of this file. In the meantime, indexing
is safe provided you limit yourself to creating topics and subtopics,
and avoid deleting or editing existing topics.
/////////////////////////////////////////////////////////////////////////////
COMPATIBILITY NOTES: (versions prior to 1.50)
Those who have used programming commands should note that message()
is now the much more powerful text() command. There are also slight
changes to play(), jump(), and jumplist(), and hotspots will have to
be redrawn (again) to conform to the new standard. See below and the
entries for these commands in MANUAL2.DOC.
Versions prior to 1.30:
As of version 1.30, compiled books created with earlier versions of
Orpheus are no longer compatible with the Orpheus Reader. Uncompiled
books are however compatible with OH.EXE, and can simply be recompiled.
If you have created Graphic, Init, or Action links, you will need
to update them to use the Orpheus Command Language, as detailed in
Part II of the User's Guide, MANUAL2.DOC. See especially Chapter 3,
"Converting Old Commands".
/////////////////////////////////////////////////////////////////////////////
Version 1.60 (May 27, 1993)
NEW FEATURES:
- The Reader now has a Formfill window in which your users can fill out
forms or questionnaires onscreen, then print them to disk or to the
printer. Use the load() command with the "form" keyword as explained
in MANUAL2.DOC.
- Protect your work and reduce file-clutter with library files! Library
files can contain forms, graphics, and ansi screens; combining many
such files into a library eliminates the average 1000 bytes per file
of wasted disk space. For distribution, library files compress more
efficiently; at runtime, Orpheus reads from them directly with no loss
in speed. FGILIB.EXE (the library manager) is free to registered
users. See Chapter 7 or MANUAL1.DOC.
- Now when starting up the Reader you can specify a card number on the
command line. This is mainly for the use of authors who wish to use
Orpheus as context-sensitive help for another program. To find out
what numbers to use, turn on "List Compiled Numbers" on the Project
Menu before compiling. For each card that you wish to load by number,
navigate to it in OH.EXE and note its "uncompiled" number on the File
Menu. After compiling, look in the .DOC file made for that project
and find the equivalent compiled number. This feature is safe: if
the specified number is for an Init or Action card, or for a card that
does not exist, the Reader loads the designated Home card instead.
Authors can also use it with the load(new...) command, setting up an
Action link that takes the user not only to a new book, but to a
specific card in that book.
/////////////////////////////////////////////////////////////////////////////
Version 1.54 (May 6, 1993)
NEW FEATURES:
- The FileView window now has essential hypertext capabilities. Using
simple text codes, you can link as many text files as you want and
have quick access to them through Orpheus.
- The load() command now lets you link to external, uncompiled text
files. Using the "text" keyword, as in load(text, filename.ext) you
can give your readers access to often-updated text files which they
can edit themselves. Files are viewed in a version of the FileView
window adapted to the Orpheus Reader. As in OH.EXE the window has
hypertext capabilities (explained in online help) which users can
extend to make links to their own text files. See MANUAL2.DOC for
details.
//////////////////////////////////////////////////////////////////////////////
Version 1.50 (March 12, 1993)
NEW FEATURES:
As promised, I've got plenty of goodies for those who enjoy working
with programmable cards. (New users please note, you don't *have*
to program in Orpheus. However, the Orpheus Command Language makes it
easy to achieve special effects with both text and graphics. These
features are explained and illustrated in MANUAL2.DOC.
- The text() command replaces message(), letting you display up to 23
lines of text with a maximum length of 74 characters in a temporary
window. Parameters give you control over the location and appearance
of the window, even how long it remains onscreen. This is ideal for
those small notes that you don't want to place on a separate card, or
for things you want to display side-by-side with other text.
- The lookfor() command lets you check to make sure the user has a
required file. Sets a flag to "okay" or "failed" accordingly, which
you can test and respond to the same as with trymode().
- The gbox() command lets you draw a filled rectangle in any graphics
mode, in the color of your choice. Coordinates can be given in pixels
or character cells (like text mode). Gbox() is ideal for setting up a
window in which to display graphics text; it can also be used to draw
boxes around small images.
- The gtext() command lets you display text in any graphics mode.
- Multiple graphics can be displayed simultaneously by using the set()
command to turn off fadein and fadeout. You can even set the video
mode, draw a graphics box with gbox(), then call graphic() to display
an image inside the box.
- The load() command lets you l