Changeset 475

Timestamp:

May 14, 2023, 5:47:12 PM (2 years ago)

Author:

ataylor

Message:

Update documentation for NewView 2.19.8.

Location:

trunk

Files:

• howto.txt (modified) (17 diffs)
• i18n/Changes.txt (modified) (1 diff)

trunk/howto.txt

@@ -4 +4 @@
 Copyright 2003-2006 Aaron Lawrence
 Copyright 2006-2019 Ronald Brill
+Copyright 2019-2023 Alex Taylor
 
 
 The major parts of the code are developed in SpeedSoft Sibyl.
 
-*Important Note*: This setup will use these updated Sibyl libraries instead 
+*Important Note*: This setup will use these updated Sibyl libraries instead
 of the ones installed with Sibyl.  Aaron has made many bug fixes and a few
 enhancements.  Some things will not build with the original Sibyl Fixpack 3
-libraries, for example some components depend on parts of the SPCC being 
-changed from Private to Protected.  (There were apparently problems with 
+libraries, for example some components depend on parts of the SPCC being
+changed from Private to Protected.  (There were apparently problems with
 Sibyl Fixpack 4 and so it is not used, although some of the bug fixes from
 FP4 are included.)
@@ -26 +27 @@
         hlpmgr          replacement for OS/2 HelpMgr.dll
                         The HelpMgr DLL is compiled with Watcom C++.
-                        It generates a DLL containing both 16 and 32 bit 
+                        It generates a DLL containing both 16 and 32 bit
                         entry points,like the original HelpMgr.dll.
                         See http://www.openwatcom.org.
@@ -62 +63 @@
    setup files.  To avoid committing working-copy-specific configuration to the
    repository, templates are provided, along with a script to generate the
-   working project files from them.  
+   working project files from them.
 
    From the top-level directory, run `project-setup.cmd`.  This will create
@@ -70 +71 @@
    This can be done by copying each of the following files to the indicated
    filename, and then replacing every instance of `@NV_DEV@` in the new files
-   with the full path of your working copy's top level directory. 
+   with the full path of your working copy's top level directory.
 
         ae\ae.spr.def                    -->  ae\ae.spr
@@ -100 +101 @@
 
 
-Conventionally, I compile the libraries (Sibyl, Library, Components) with 
-debug information.  You can then turn debugging on or off when compiling 
+Conventionally, I compile the libraries (Sibyl, Library, Components) with
+debug information.  You can then turn debugging on or off when compiling
 NewView itself; if debugging is off, the library debug info will be discarded
 at link stage.
@@ -115 +116 @@
 
 The Components project (`Components\Components.spr`) contains the updated
-Sibyl controls used by NewView and other projects (including custom ones 
+Sibyl controls used by NewView and other projects (including custom ones
 such as the rich text viewer).
 
-For the Sibyl IDE to be able to use these classes, they are compiled into 
+For the Sibyl IDE to be able to use these classes, they are compiled into
 `CompLib.DLL`.  When building applications like NewView, however, the object
 files will be linked statically into the application.
 
 The `makeall.cmd` script in the `Components` directory will rebuild all the
-object files (and the test app, `Components.EXE`.  To rebuild `CompLib.DLL`, 
+object files (and the test app, `Components.EXE`.  To rebuild `CompLib.DLL`,
 load `Components.spr` in the Sibyl IDE and rebuild it.
 
-*Note:* Because the IDE requires `CompLib.DLL` to actually load a project 
+*Note:* Because the IDE requires `CompLib.DLL` to actually load a project
 using those classes, and the Components project includes a demo form with the
-classes on it, this rather unintuitively means that you can't build 
-`CompLib.DLL` unless a previously-built `CompLib.DLL` already exists.  For 
+classes on it, this rather unintuitively means that you can't build
+`CompLib.DLL` unless a previously-built `CompLib.DLL` already exists.  For
 this reason, a prebuilt version with all the new/modified classes is included
-in this repository.  
+in this repository.
 
 
@@ -144 +145 @@
 
 To build a release version, you should build the executables from the GUI.
-When doing this, make sure that the directories `build\newview` and 
-`build\newview_stub` exist and are writable. 
+When doing this, make sure that the directories `build\newview` and
+`build\newview_stub` exist and are writable.
 
 To build NewView.EXE from the GUI, open the project file `NewView\NewView.spr`
-from the Sibyl IDE.  You should be able to build it from the Project menu.  
+from the Sibyl IDE.  You should be able to build it from the Project menu.
 NewView.EXE will be placed in the `build\newview` directory.
 
@@ -157 +158 @@
 above for details.
 
-You can build ViewStub.EXE from the GUI in the same way as NewView.EXE, by 
+You can build ViewStub.EXE from the GUI in the same way as NewView.EXE, by
 opening `NewView\ViewStub.spr` in the IDE and building it from the Project
 menu.  ViewStub.EXE will be placed in `build\newview_stub`.
@@ -167 +168 @@
 in the `build\hlpmgr` directory.
 
-Alternatively, if OpenWatcom is available in PATH, INCLUDE, and LIB, you can 
-run `wmake` directly.  However, note that the Watcom C makefile for HelpMgr 
-will build hlpmgr2.dll by default.  To build helpmgr.dll instead, build with 
+Alternatively, if OpenWatcom is available in PATH, INCLUDE, and LIB, you can
+run `wmake` directly.  However, note that the Watcom C makefile for HelpMgr
+will build hlpmgr2.dll by default.  To build helpmgr.dll instead, build with
 `wmake helpmgr.dll` (which `makeall.cmd` does).
 
-helpmgr.dll is normally in use by the WPS (WorkPlace Shell, the desktop) so to 
-put it into use, you must either use a DLL-unlocking utility like replmod (on 
-Hobbes.nmsu.edu) or boot to a command prompt, and replace the dll in 
+helpmgr.dll is normally in use by the WPS (WorkPlace Shell, the desktop) so to
+put it into use, you must either use a DLL-unlocking utility like replmod (on
+Hobbes.nmsu.edu) or boot to a command prompt, and replace the dll in
 `c:\os2\dll`.
 
@@ -184 +185 @@
 ### NewView DLL ###
 
-Go to the `newview_dll` directory and run `makeall.cmd`.  Or, if OpenWatcom 
-and PMPrintF are already installed and available in PATH, INCLUDE, and LIB, 
+Go to the `newview_dll` directory and run `makeall.cmd`.  Or, if OpenWatcom
+and PMPrintF are already installed and available in PATH, INCLUDE, and LIB,
 you can simply run `wmake` directly.
 
@@ -191 +192 @@
 ### Help & Language Files ###
 
-The NewView help file was is in .ipf format and can be compiled with the 
+The NewView help file was is in .ipf format and can be compiled with the
 OS/2 IPFC compiler.  The language files use Aaron's language support module
 (see `NewView\Design.txt` for technical information) and are simply structured
@@ -197 +198 @@
 
 Run `makeall.cmd` from the `i18n` directory to build/copy all the help and
-language files.  Each language lives in a subdirectory with its own 
+language files.  Each language lives in a subdirectory with its own
 `makeall.cmd` that gets called by the parent script.
 
@@ -206 +207 @@
 is the old standalone installer for NewView.  The project will create the
 executable NewViewInstall.EXE - you are recommended to rename it to install.exe
-if you need distribute it as part of a NewView installation ZIP file.  
+if you need distribute it as part of a NewView installation ZIP file.
+
+Make sure steps 1-3 above have been completed.
+
+Also make sure the directory `build\installer` exists and is writable.
 
 The install executable requires Aaron's renmodul.dll, a copy of which is in the
@@ -225 +230 @@
     install.exe         (from build\installer)
     renmodul.dll             (from installer)
-    gpl.txt                     (from newview)
+    gpl.txt                     (from i18n)
+    Changes.txt                 (from i18n)
+    readme.txt                  (from i18n)
     (language files)            (from build\newview_i18n)
 
@@ -242 +249 @@
 Make sure steps 1-3 above have been completed.
 
-Also make sure the directory `build\ConfigApps` exists. 
+Also make sure the directory `build\ConfigApps` exists.
 
 Open the project file `ConfigApps\ConfigApps.spr` in the Sibyl IDE.  You should
-be able to build it from the Project menu.  ConfigApps.EXE will be placed in 
+be able to build it from the Project menu.  ConfigApps.EXE will be placed in
 the `build\ConfigApps` directory.
 
@@ -254 +261 @@
 Make sure steps 1-3 above have been completed.
 
-Also make sure the directory `build\AE` exists. 
-
-Open the project file `ae\ae.spr` in the Sibyl IDE.  You should be able to build 
+Also make sure the directory `build\AE` exists.
+
+Open the project file `ae\ae.spr` in the Sibyl IDE.  You should be able to build
 it from the Project menu.  AE.EXE will be placed in the `build\AE` directory.
 
@@ -269 +276 @@
 They should not be needed anymore, but are included for posterity.
 
--- 
+--
 
 2. Unzip all files.

trunk/i18n/Changes.txt

@@ -1 +1 @@
 NewView release changes
+
+V2.19.8
+- Fix: Controls and dialogs should now scale more reliably when using large fonts.
+- Tweak: The Application Font setting, if not set explicitly, defaults to the global
+   Presentation Manager window text font.
+- Tweak: Updated contact info links on product info dialog.
 
 V2.19.7