Next Release
 Some plans for the Next Release
------------------------------------------------------------------------------

 The Expand Library is a dynamic product.. That's why there might be
 some plans for the future. This is a tentative list of possible
 enhancements, no guarantees can be given at all.

 Note that you may give suggestions. The idea of the Expand Library is to
 remain a general purpose addition to Clipper, with lots of options and
 possibilities.

 DOS 4 and DOS 5 Features:
 The current version of the Expand Library is based on DOS 3.30, meaning
 that it supports enhancement provided by that version (and higher) of DOS.
 Currently, no additonal features of DOS 4 and 5 are used. Future versions
 of the Expand Library might use features (including Internal ones) of those
 versions of DOS, possibly also DR-DOS features.

 Netware Functions:
 A limited number of Novell Netware functions might become available. Those
 functions will be specifically tailored to what a Clipper Developer would
 possibly require from Netware APIs. So don't expect functions that will
 report the number of cache hits/misses on a selected server, but rather
 the Login Name of a user, the Server name, Group membership etcetera.

 i386 Support:
 The current version of the Expand library can be run on all computers,
 future enhancements might contain functions that would run only on i386
 computers, where some of the features of this chip might be used to improve
 speed (eg. PCX displaying).

 Interface to Other Software:
 By means of the "MultiPlex" interrupt, there is a way for resident software
 to communicate with Applications. Future versions of the Expand Library will
 support some interfaces to Resident Programs (eg. Interface to QEMM, XMS/EMS
 info). Possibly interesting stuff, but I still have to look which parts of
 such an interface can be of interest to Clipper developers.

 Graphic Functions:
 A very limited list of Graohical Functions might be included.

 Support For NG Attributes:
 Currently, the Norton Guides routines do not support Attributes that are
 present in the Norton Guide. They are simply stripped out of the resulting
 text. When possibilities to control the displaying of the string using
 TBrowse and possibly a TMemo become better, options could be added so that
 attributes are interpreted when reading guides.

 And..
 Anything that comes across. If you have suggestions don't hesitate to make
 them. A number of general purpose functions are in the pipeline at this
 moment. There are lots of ideas, but one needs to test them thoroughly before
 making them available to the public.