RELEASE NOTES FOR XVT/Power++ RELEASE 2.0, Jan. 14, 1994
========================================================
This readme is for XVT/Power++ 2.0. This readme and the
Power++ Release 2.0 documentation define the scope of
functionality for this product.

This file contains the following sections:

SECTION I

       	1.  NEW FEATURES
       	2.  PRODUCT CONTENTS
       	3.  INSTALLATION
       	4.  USAGE
            a. Using the makefiles and IBM-WorkFrame/2 projects
            b. Compiling the Power++2.0 Library
            c. Compiling the Examples
            d. Using the Power++ Shell Project
            e. Linking note
        5. BUG LISTINGS

SECTION II (Customer Support)
        GETTING TECHNICAL HELP



	SECTION I (General Information)


1. NEW FEATURES
---------------

Layout: A new tool for laying out Native object and Windows. Layout will also
generate a Shell Application Frame Work.

Resources: Native object and Windows can be built through Native URL
generated resources.

Automatic Data Propagation: Direct support for Model View Controller paradigm.

Menus: New classes provide full encapsulation of XVT menus.

Root Objects: Two new root object are provided for future work.

XVT/Power++ 2.0 requires XVT/PM Portability Toolkit Release 3.01 or later.
In addition to the previous requirements, make sure you have read the 
XVT/PM Portability Toolkit installation requirements and that your
system complies.

This version of XVT-Power++ for OS/2 PM does not currently support dynamic
sizing and moving of native views (controls).


2. PRODUCT CONTENTS
-------------------

** Source Distribution

There is one distribution disk:

       	XVT/Power++ 2.0

The files and directories contained in this product are:

Disk 1 of 1:
 ROOT directory
       	readme - latest release information (this file)
       	xvtpwr\src
       	xvtpwr\include
       	xvtpwr\lib
       	xvtpwr\doc
       	xvtpwr\bin
       	xvtpwr\demo
       	xvtpwr\demo\shell
       	xvtpwr\demo\hello
       	xvtpwr\demo\ss
       	xvtpwr\demo\ask
       	xvtpwr\demo\sprdshts
       	xvtpwr\demo\draw
       	xvtpwr\demo\edit
       	xvtpwr\demo\drag
       	xvtpwr\demo\hardhat
       	xvtpwr\demo\resource
       	xvtpwr\demo\model



3. INSTALLATION
---------------

	Refer to the product installation sheet for information on
	installing XVT-Power++. The default installation path is
	<drive>:\xvt\xvtpwr. This is sibling to the default installation
	path for XVT/PM (<drive>:\xvt\xvtpm).  

Set up your environment:

        The INCLUDE environment variable should have the XVT-Power++
        include directory appended to it.

Project notes:

        It is important that for FAT file systems, DOS be defined for
	curl.exe, source, and new projects.


4. USAGE
--------

a. Using the makefiles and IBM-WorkFrame/2 projects

	WorkFrame projects may be used for the source and examples. 
	However, the makefiles supplied have been modified for various
	reasons. The source makefile creates a library and copies this
	library into the xvtpwr\lib directory. The examples use the CURL
	mechanism for portable resources. We suggest that you modify the
	makefiles by hand and NOT let WorkFrame create them for you.

        Note:

        It is important that the INCLUDE, LIB, and PATH environment variables
	be set to include the XVT/PM toolkit and XVT-Power++ library
	respectively.

        e.g.  INCLUDE = ...;C:\XVT\XVTPM\INCLUDE;C:\XVT\XVTPWR\INCLUDE;
              LIB = ...;C:\XVT\XVTPM\LIB;C:\XVT\XVTPWR\LIB;
              PATH = ...;C:\XVT\XVTPM\BIN;

        Also, you may need to modify the XVT_LIB path variable in all of the
        makefiles. See section e. below regarding linking.


b. Compiling the Power++2.0 Library

        The libraries come compiled, but you may recompile them yourself.
        The project and makefiles for source builds the libraries (and .obj's)
        in the src directory.  


c. Compiling the Examples

        Appropriate makefiles are located in each of the example directories.


d. Using the Power++ Shell Project

	XVT-Power++ 2.0 now includes Layout 1.0 which can be used for
	generating an initial application.  See the XVT-Layout section
	in the manual for more information.

e. Linking note
        When linking, C-Set++ will generate a warning prompt regarding a
        migration library (dde4mbm.lib). Press "Enter" at this prompt to
        continue linking.

5. BUG LISTINGS
---------------

        Please see the release notes for XVT-Power++ bug listings.


SECTION II (Customer support)


GETTING TECHNICAL HELP
----------------------
For technical assistance with your XVT product, please contact us via 
e-mail, BBS, or phone. Phone support is available during the hours 8 AM
to 5 PM Mountain Time, Monday through Friday. Your call is always welcome.
Please use the service request form below, or have this information available,
when you contact us. You may contact the Customer Support Department using
the following methods:

       	Address:
       		XVT Software Inc.
       		Box 18750
       		Boulder, CO 80308 USA
       	Voice: (303) 443-8XVT
        CompuServe Mail address: 75765,1233
        Internet: techsup@xvt.com
        or send XVT Bulletin Board mail.

Note: If you purchased your XVT product through a distributor, please contact
this distributor for technical assistance.

For XVT Bulletin Board System sign-on and instructions, contact customer
support. This service is available to all registered users of XVT with
current maintenance agreements.


Service Request Form:
---------------------------------cut here-------------------------------------

        				--XVT SERVICE REQUEST--

         Date:                              Serial Number:
Customer Name:                                XVT Product:
 Company Name:                                XVT Version:
 Phone Number:                                   Compiler:
         Fax Number:                              Computer Type:
Email Address:                           Operating System:
         SR #: (if applicable)             Window Manager:
        				     Memory Model: (XVT/Win customers)

Question or Problem Description:



-------------------------------------end--------------------------------------
[End of readme]
