home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Education Master 1994 (4th Edition)
/
EDUCATIONS_MASTER_4TH_EDITION.bin
/
files
/
wordmisc
/
orphes1
/
oh1.exe
/
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 load a whole new book! For example, you
could have a trilogy of electronic novels, and in each one include
a little menu with Action links through which the user can go directly
to one of the others.
- The jump() command now accepts a number representing the card from
which you can "pretend" to have jumped, useful if repeatedly returning
to a Contents or Menu card where you would like the last-used linkword
to be hilited on return.
- Now ansi screens can have hotspots! The rules are the same as for
putting hotspots in real graphics; see MANUAL2.DOC for details.
- The FileView window now offers a super-fast way to import text from
long external files. Selecting "AutoMark" instantly marks a full
23-line block. The prompt then turns to "AutoMORE", and if you select
it again, Orpheus automatically appends a More link to the card in
the current Edit window, jumps to it in the background, and copies in
the block from FileView. In other words, pressing <A> twice grabs a
23-line chunk and adds it to your work in a brand new card. (You could
do the same thing with a macro, but this is faster.) AutoMark even
lets you grab only as much as you want by resizing the block with the
Up/Down and PgUp/PgDn keys.
/////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////
COMING SOON IN 1994! -- *** ORPHEUS 2.0 ***
I don't usually talk in public about future releases, but with version
2.0 I can't resist. Here's a brief rundown of what's done already:
- Multimedia: support for GIF files, SuperVGA, and Soundblaster-
compatible sound cards (plus a few others). Play standard MIDI,
WAV, VOC files and others. Hotspots in graphics can now be linked
to just about anything. You can link a word or part of a graphic to
a piece of music, or set music playing automatically. Music plays
continuously while the reader explores your work. Authors working
entirely in graphics mode will find that they can now make sure the
Orpheus Reader never slips into text mode or displays anything except
just what they want their users to see.
- Finished products: distribution is simplest with the smallest number
of files. Now you can compile even a very large document into a
single HTX file, optionally including the Reader's online help.
Or compile something huge into files that are no bigger than the
size you specify. Orpheus will also provide better compression of
compiled works, with guaranteed encryption of anything too small to
compress efficiently.
- Script commands: for normal hypertext you still don't have to write
any scripts at all, but for authors who want the power, Orpheus 2.0
has some nifty new stuff. Link to an Action card containing an
open() command, and you have controlled access to all dialogs in
the Orpheus Reader, e.g. open(help), open(notepad), etc. Set up
your own dialogs with the new ask() command: Orpheus figures out
where to place everything, and you get a bullet-proof dialog just
like the ones I've written for Orpheus, with up to 19 lines of text
and up to 6 user-selectable choices. The new "answer" keyword lets
you check the user's selection and branch accordingly. Or make your
own popup menus with the new menu() command, linking choices either
to parts of your work or to internal Reader commands such as the
menus, dialogs, etc.
- Reader interface: Orpheus 2.0 gives authors extensive control over
the interface in the Orpheus Reader. If you wish, you can completely
turn off access to the standard interface -- keystrokes, menus, the
titlebar -- and replace it with your own menus and command buttons.
You don't *have* to design your own interface, but if you want to
you'll have that power, and it really is easy to handle.
What else? Most of what I've just described is finished, but there
are still some important things I want version 2.0 to have, such as
scrollable text cards, fonts, and full-text search in the Reader.
In January 1994 Orpheus will go into beta testing, and while the
testers have their fun I will begin work on an all-graphics version
of the Reader. This will let me provide the one feature for which I've
heard the most requests: easy combination of text and graphics on the
same screen.
And a whole lot more!
Rod Willmot
December 9, 1993