Click above to get retro games delivered to your door ever month!

Anticipated schedule of di_Library features

   In general, each scheduled feature is anticipated to be completed no
   later than in the version number in which it is indicated.  Changes in
   functionality may be made during the course of Alpha/Beta development in
   response to user feedback and/or reevaluation by the programmer.
   However, the basic goals of implementing a drop-in replacement
   output-neutral input/output system for Clipper, with particular focus on
   enabling Web access, shall be retained.  Understandably, I get a bit
   less specific as versions go up.

   Library functions intended for use by third party programmers are named
   in the manner di_FUNCNAME(); functions intended primarily for internal
   use by di_Library are named as _diFUNCNAME().  In Alphas and Betas it
   may be necessary to use internal functions to achieve certain results
   which will be possible in later version using only the (more
   error-resistant) user functions.

     0.1
     Implementation of most basic Clipper user input/output primitives,
     and general functions used to reference devices:

     0.2
     Implementation of additional Clipper i/o elements:  Additional input
     controls.
         di_GetList()             // Replacement for @..GET LISTBOX
         di_GetCheck()            // Replacement for @..GET CHECKBOX
         di_GetPush()             // Replacement for @..GET PUSHBUTTON
         di_GetRadio()            // Replacement for @..GET RADIOGROUP

     0.3-0.5
     Implementation of more complicated Clipper i/o elements:  Table and
     menu controls.
         di_Prompt()              // Replacements for PROMPT/MENU TO
         di_MenuTo()              //    menuing system
         di_TBrowse()             // Replacement for DB display object
         di_TopBar()              // Replacement for TopBar object
         di_PopUp()               // Replacement for Popup object

     0.6-0.7
     Implementation of CGI specific functions.  Need to create functions
     to parse CGI parameters, deal with CGI environment variables,
     implement hooks for web-server specifics.  Possibly implement some
     detection of web-browser feature sets.

     0.8
     Creation of higher level input/output functions.  Such custom
     functions would not be drop-in replacements for native Clipper
     commands and functions, but would provide ready methods of
     performing the most used i/o activities in an output-neutral manner.

     0.9
     Creation of additional functions specific to HTML layout and
     presentation.  These functions will not be output-neutral, but will
     allow specific tweaking of the appearance of created web pages.

     1.0
     Any final bug-fixes and gap filling which arises during Betas.
     Creation of a feature-stable packaged product for wider distribution
     efforts.