
 Readme for HWGUI utilities
 __________________________
 
  $Id: Readme.txt 3417 2023-12-15 11:14:55Z alkresin $
 
 Here you find some important utility programs for
 developers of HWGUI programs.
 
 For details for every utililty read the files Readme.txt
 in the listed subdirectory above and the
 recent HWGUI HTML documentation in main directory "doc".
 
 The port to GTK3 is under construction.
 There are some trouble with the design of dialog elements, see
 file doc/GTK3.txt for details.


  bincnt \
  ========

  The "binary container" is a feature to avoid
  lot's of small binary files in the installation directory
  of your HWGUI application.
  Only one container file is needed to collect them all.
  This could be image files (*.ico, *.bmp, *.jpg, ...)
  and other special binary files.
  It is the best solution for multi platform applications,
  for example to avoid the usage of the Windows resource
  compiler.
  The default file extension for binary container is *.bin.

  The utility "Binary container manager" is for creating and
  editing binary container and is placed
  with source code and build scripts in directory "utils/bincnt".

  For usage instructions see the inline comments of sample program
  "samples/bincnts.prg".

  
  dbc \
  =====

  or DbcH:
  Data Base Control (Harbour)
  is an utility that allows complete
  multiuser access and indexes.
  For details read file "hwgui\utils\dbc\Readme.txt".


  debugger \
  ==========

  The HWGUI visual debugger.

  Source code and build scripts in directory "utils/debugger".
  Build and usage instructions in text file "readme.eng",
  also available in russian language as "readme.rus".  


  designer \
  ==========

  The HWGUI Designer:

  The Designer is intended to create/modify input screen forms and reports.
  For details read the HTML documentation "doc/hwgdoc_misc.html",
  chapter "7.1. Designer" and the file Readme.txt in the subdirectory.


  devtools \
  ==========

  HWGUI devloper tools:

  In the subdirectory "devtools" you find some more helpful utilities
  for programming and bugfixing of Clipper, Harbour and HWGUI programs.
  For details look into file "Readme.txt" in this directory.    


  editor \
  ========

  The HWGUI editor:

  The main goal of this project is testing of a class HCEdiExt,
  which is intended to be used for an embedded rich text editor in applications,
  written on Harbour + HwGUI.
  Read more in documentation of the editor.

  You find source code and documentation in directory
  "utils/editor".

  For introduction read file "utils/editor/Readme.txt".


  hbpad \
  ========

   A notepad like, plain text editor, based on HcEdit class.


  hwbuild \
  ==========

  A hbmk like utility, which is intended to build Harbour applications, especialy - GUI applications.

  tutorial \
  ==========

   The HwGUI tutorial:

   Learn more about HWGUI:
   Compile and run the editorial in directory utils\tutorial
   Interactive - because you
   can not only read the code and comments, but execute it. Moreover,
   you can edit the code and then execute it immediately to see the
   results of your changes.  
   
   Build scripts:
   
   bldgw.bat     for MingGW on Windows 
   bld.bat       for Borland C
   bldow.bat     for OpenWatCom C on Windows
   bldgtkwin.bat for Windows with GTK+ (cross development environment), only for test purposes.
   build.sh      for LINUX with GTK+2
   hbmk.sh       alternative script using the Harbour hbmk2 utility, 
                 calls hwgrun.hbp and tutor.hbp
         
   For GTK3 edit files hwgrun.hbp and tutor.hbp:
   #{linux}../../hwgui.hbc
   # GTK3: Deactivate previous line
   # and activate following line
   {linux}../../hwguiGTK3.hbc
    
   and build the tutor by typing:
   chmod 755 *.sh
   ./hbmk.sh

 
  statichelp \
  ============

  Create static help texts, that will be contained
  in your created EXE file, so no external files or
  databases containing the help text's.
  Allows easy handling of help text's.

  Also the codepage is predefined to UTF-8,
  so that you have no display trouble on
  Windows, which is not supported UTF-8 by the
  system.

  See the instructions in the Readme.txt file
  in the sub directory.
  
  
   
========================== EOF of Readme.txt ==================================
