         Clarion for Windows Beta 3

         Table of Contents:

         1. What's new to Beta 3
         2. Notes for Beta 2 users
         3. Program Setup
         4. Release Notes for Beta 3
         5. Template notes
         6. Known Problems
         7. Btrieve Distribution
         8. Additional Document files
         9. In the Works

1. What's new to Beta 3
-----------------------
Here Are the New Features You'll Find:

. The most important addition to Clarion for
  Windows Beta 3 is the Application Generator.
  The Application Generator can now create
  complete applications using the
  preliminary templates we've included.

. Beta 3 also introduces Code Templates. You
  can use the Code Templates to automatically
  add executable code at embedded source code
  points. A dialog box prompts you with entry
  fields and lists, then creates the code for
  you. This could be the end of hand-coding
  as we know it!

. We've included the new TopSpeed file driver.
  This driver reads and writes our new proprietary
  file format very, very fast. We're not ready to
  release benchmarks yet, but we think you'll
  be impressed. The Topspeed driver can store
  multiple data files, keys and indexes in the
  same DOS file -- allowing you to open multiple
  files using a single DOS file handle.

. Almost all the connections between parts
  of the IDE are now functional. For example,
  when you specify a picture for a field with
  the data dictionary, the Application Generator
  automatically adds the correct attributes
  for the controls you place in dialog boxes
  while using the Window Formatter.

. The User's Guide includes an illustration
  showing the connections between IDE components.
  See the "Application Development Flowchart" on
  page 19. That chapter provides a brief "walk-
  through" outlining the steps for creating an
  application. The User's Guide is all new, and
  represents a new "Task-Oriented" approach to
  Clarion documentation.

. There is complete on-line help, which includes
  the entire Clarion for Windows Language
  Reference, and the text of the User's Guide.
  Note: we've provided a hard copy of the Table
  of Contents for the Language Reference, and the
  Users guide to make finding what you need easier.

2. Notes for Beta 2 users
-------------------------

The default install path has been changed from \CDDW to \CW.  You can of
course override the install location.  If you choose to install to \CW,
make sure your path is updated to reflect \CW\BIN !

You should delete your VBX registrations, and re-enter them.

Dictionary files created with Beta 2 must be re-created!

The changes to AUTO attribute and DISPLAY may cause programs
that used to work in beta-2 to fail. Symptoms are controls not
being updated correctly. See item 3. "Release Notes for Beta 3":
"New Non-stop mode" for details.

3. Program Setup
----------------
When the install finishes you are prompted to Update your Autoexec.bat,
remember that you'll have to reboot before the PATH change takes effect.


   CDDW Initialization
   --------------------
   When you run CDDW for the first time, you will be notified that CDDW had
   not been run before, and a prompt will ask "Do you want to install CDDW?".
   Answer YES to have CDDW to configure WIN.INI and create the CDDW.INI.


4. Release Notes for Beta 3
---------------------------

* You cannot have the Dictionary and Application open at the same
  time. This is a restriction for this version only.

* NIL-checking compiler option should not be turned on as incorrect
  code can be generated (It has been disabled in the project options
  dialog)

* Groups cannot currently be created in the dictionary editor (although
  they may be imported)

* The changes to AUTO attribute and DISPLAY may cause programs
  that used to work in beta-2 to fail. Symptoms are controls not
  being updated correctly. Changes are as follows:

  New Non-stop mode
  =================
  Pretty much as per Clarion 3.0, there is now a non-stop mode to
  simplify validation code. Non-stop mode is entered by calling SELECT
  without a parameter. When in this mode, whenever no other events
  are pending, the library will generate an ACCEPTED event for the
  next control in the current window which has a USE variable.
  This cycle continues until one of the following:

  1.      SELECT is called with a parameter.
  2.      window{PROP:nonstop} is set to zero
  3.      All fields with use variables have been processed.
          In this case an EVENT:Completed is posted to the window.
  4.      The control for which the accepted would be generated is
          a REQuired entry control which has not been completed.
          In this case, the field is selected automatically.

  The program can test window{PROP:nonstop} to determine whether it is
  in non-stop mode, and can set this property nonzero as an
  alternative way to enter it.

  Fields are processed in the numerical field-equate label order.


  DISPLAY, ACCEPT, and the AUTO property
  ======================================
  In Clarion 2.x and 3.x, USE variables are copied to the screen
  only when DISPLAY or ACCEPT is called for that field.
  Hitherto, in Clarion for Windows, all USE variables for all
  open windows were copied to screen at the end of EVERY
  accept loop. The library is now changed as follows:

          USE variables on a window which is not the top window on
          its thread are NEVER copied to screen.

          USE variables for STRING controls on the top window on
          each thread are copied to screen at the end of each ACCEPT loop.

          USE variables for other controls are copied to screen
          when DISPLAY is called for that control, or when an event
          is generated for the control.

  A new window attribute PROP:Auto (currently run-time only, but will
  be supported by screen formatter in due course) causes all USE variables
  for that window to be checked at the end of any accept loop.

  In Clarion 3.0, a variable is automatically DISPLAYed when you
  call ACCEPT for its field. Clarion for Windows will automatically
  DISPLAY the variable of the current FIELD() after an EVENT:Selected
  has been processed.

* You are NOT required to load SHARE.EXE to run the CW environment.

  There appears to be a serious bug in SHARE.EXE supplied with MS-DOS 6.x.
  Usually when a file is opened, SHARE will write some information into an
  internally maintained buffer.  It appears that when a large number of
  files are being manipulated SHARE overwrites the end of this buffer
  corrupting whatever data appears after it in memory.  Under Windows this
  tends to result in a GPF.  The symptoms are infrequent, and cannot be
  duplicated consistently.  The problem may be alleviated by increasing
  the buffers used by share, the defaults are:
          SHARE /F:2048 /L:20

* APP, DCT and TRF file formats are expected to change between this and the
  release version of CDDW.  However, Clarion will provide a method to
  migrate your .APPs and DCTs.


* Clarion Database Developer for Windows Bitmap Support
  =====================================================
  CW Beta 3 supports three new graphic formats, PCX, GIF & JPG in
  addition to BMP & WMF supported in earlier versions.

  PCX Support
  ===========

  Support is provided for 16 and 256 color pcx files using formats up to
  (and including) version 5. Both un-encoded and run-length encoded
  sub-formats are supported.

  PCX files load slightly slower than BMP files and require additional
  run-time memory for expansion but are often significantly smaller than
  BMP files on disk.

  GIF Support
  ===========

  Support for 2, 16 & 256 color GIFs using encoding standards 87a & 89a,
  interlaced and non-interlaced.

  These files load slightly slower than PCX files but can be smaller when
  large areas of block color are used.

   We are required to state that:

      "The Graphics Interchange Format(c) is the Copyright property of
      CompuServe Incorporated. GIF(sm) is a Service Mark property of
      CompuServe Incorporated."

  JPG Support
  ===========

  The JPG format is capable of very significant image compression
  particularly on photographic and scanned images. The JPG format can
  also handle 24 bit color images although currently they are converted
  to 256 colors for display in CDDW.

  JPG is 'lossy' that is to say it gets its compression from removing some high
  frequency detail from the pictures. This is not usually visible to the
  human eye and is thus ideal for displaying pictures for viewing.

  In order to get the best possible image from the JPG file,
  sophisticated color dithering techniques are used which makes the JPG
  format the slowest to load (although once loaded images will redraw at
  full speed).

  The JPEG standard does not specify all details of an interchangeable
  file format.

  For the omitted details we follow the "JFIF" conventions, revision 1.02.

  Some products (especially older ones) have not followed these
  conventions. In particular the GIF2JPG program produced by Handmade
  Software will only produce compatible JPG files when used with the -j
  switch.

  For maximum compatibility we have based our JPG reader around a widely
  accepted and available set of sources.

  -This software is based in part on the work of the Independent JPEG Group-

5. Template notes
-----------------

The Templates do not yet support the following:

   * Referential Integrity enforcement code
   * Multi-user Concurrency checking
   * On-screen enrty fields used as a Range Limit for a Browse procedure.
   * There is not a REPORT template yet

6. Known Problems
-----------------
* Source Generation
  No events are generated for Checkboxes, hence you cannot attach code to
  a checkbox.

* Dictionary Import from CDD to CW -

During testing of the CDD to CW Dictionary Import we have found that some
Version 3.0 Dictionary files will cause the import function to enter an
endless loop.  We have not yet determined what is causing this to happen.  It
appears to happen when a file does not have a key defined and it happens to
be the last file defined in the DCT.  You may have to add a Key definition to
the file to get the import to terminate properly.  We would appreciate a
copy of any DCT that does not import properly.

* The Fields & Keys listboxes do not have any titles. The Fields are listed in
the Left List Box and the Key definitions are in the Right Listbox.

* Groups are not supported in the Dictionary at this time. Groups can be
imported but not maintained.  If you use GROUPs, you can maintain your
.DCT in CDD 3.0 and import it for your Windows APP.

* Using @P picture token for data entry, requires that the "Entry Patterns"
checkbox be checked in the Expanded Windows Properties Dialog.   Failure to
check the "Entry Patterns" will result in strange behavior of Pattern Picture
tokens at runtime.

* You MUST end your source files w/ a CR LF. If the source does not end with
a CR LF the compiler will give an Invalid Character Error.

* MultiThreaded windows are not supported directly by the Templates.
You will have to manage data flow between threads yourself, and check for
data conflicts.  Template HELP describes some of the issues on multithread,
refer to Topic "Actions".


7. Btrieve Distribution
-----------------------
Due to changes in the license requirements by Btrieve Technologies Inc.,
you CANNOT distribute the Btrieve DLL's that Clarion ships with CW.
Clarion is currently re-negotiating with BTI for redistribution rights
for the final product.  However, you may obtain your own unlimited
distribution license from BTI for $300.00 .  To order call 1-800-BTRIEVE
and ask for the Btrieve Client Engine for Windows v6.15.

8. Additional Document files
----------------------------
File Driver information:

     ASCII.DOC   - Ascii
     BASIC.DOC   - Basic
     BTRIEVE.DOC - Btrieve
     CLA21.DOC   - Clarion
     CLIPPER.DOC - Clipper
     DBASE3.DOC  - DbaseIII
     DBASE4.DOC  - DbaseIV
     DOS.DOC     - DOS
     FOXPRO.DOC  - Foxpro
     PARADOX3.DOC- Paradox
     TPSDRV.DOC  - Topspeed

Open DataBase Connectivity
     ODBC.DOC

Source/Screen Code conversion:
     CLWCNV.TXT

ChartBuilders Graph VBX control:
     GRAPHVBX.DOC

9. In the Works
----------------

User interface improvements
===========================

Here is a short list of some of the more commonly requested
improvements that we intend to implement before the final version.
Please let us know if you have any other suggestions for improvements.

Editor Keys will be re-definable (from the INI file).

Editor will support Keyboard macros (single window text and editor
command sequences invoked by a single key).

Embedded editing (e.g. from the application generator) will be improved,
with fully modal windows for editor and screen and report formatters.

Screen and report formatting will have font name/size/style setting from
the toolbar. You will also be able to set the use variable from the toolbar.

Control property dialogs in screen and report formatters will be improved,
and the More/Less buttons removed (with dialogs fully expanded).

You will be able to change working directory, to maintain different
projects in different directories.

There will be automatic session saving which will be application/project
based. (This will save current working directory and redirection file).

New and Open file types will be more intuitively ordered and user
redefinable. The user will be able to add new file extension mappings.

Control templates, field prompts and improved embedded source entry will
be supported within the application generator. Also it will be possible to
insert a new field from within the screen and report formatters.

Printing will be supported from the editor

You will be able to choose other (monospaced) fonts for the editor.

File redirection will work on open dialogs if file not found in specified
directory.

Syntax coloring in editor will be improved and will support template files.

Global replace in editor will not update the screen until finished.

Error editing will cross multiple files, and errors will be
highlighted more effectively.

The list box editing dialog will be substantially improved (hopefully
making it more intuitive to use)
There also will be a picture editing dialog accessible from the 'more'
button (...) next to picture entry fields.

