Typo
Repair of bad HTML links
Link repaired
Integration of StringTemplate V4.3.4 into the project. The jar file has been build with Open JDK Java 8 (1.8), which is required for compatibility with MATLAB R2021b. MATLAB fails to recognize the jar, when built with an up-to-date Java. Octave doesn't have this problem
Javadoc comments
Typos
Temaplate modified in order to adopt the new, more transparent behavior of StringTemplate 4.3 with respect to blank lines at beginning and end of sub-templates.
Reference to last recent SVN revision
Compiler sample script still references previously uses Java jar for ST4
Octave start script updated, more recent version of Octyve considered for PATH setting
Documentation changes, still some bad references found
Documentation changes, still some bad references found
Minor documentation change
Missing file added to source control
Rebuild of jar after increment of version designation
There's no change of the Java source code but some documentation changes have been made in the M scripts and we increment field build of the version designation
Migration to new revision 4.3 of StringTemplate.
There's no change of the Java source code but some fixes have been made in the M scripts and we increment field fix of the version designation
There's no change of the Java source code but some fixes have been made in the M scripts and we increment field fix of the version designation
There's no change of the Java source code but some fixes have been made in the M scripts and we increment field fix of the version designation
How to run the initial sample?
Re-testing with MATLAB 2019 had revealed some compatibility issues:
Fix: A missing definition of a constant value. This script error has not been found before as it takes effect only in a very rare failure situation. Recent compatibility tests with MATLAB 2019 have now discovered it
The library ST4ForOctave had been published under the terms of the GNU Lesser Public License but several scripts still had inside the copyright notice of the GPL
Compatibility with MATLAB 2015b
Compatibility with MATLAB 2015b ensured
Documented revision number corrected
Update of readme to recent changes
Link to local Javadoc of service object info added.
Documentation: Reference to Javadoc of new service object info added
Minor text corrections
Changed behavior of mechanism to locate template group file documented
Merged revision(s) 22-38 from branches/dev-infoObject, development branch is closed herewith. Major changes are:
File generation from template now permits to write the new file in a not yet existing directory. mkdir is applied to make the directory prior to file generation.
Cleanup of samples: Templates separated from user called Octave scripts. Templates collected in new folder "templates". Deprecated calls (clear cache, Boolean verbose) replace with new equivalents. Obsolete script for adding paths, addOctavePaths.m, removed.
Fix: Warning emitted about clearing cache although not appropriate
New test case added for st4RenderWrite.m
Let the input variables u and z have an observable impact on the printed program output when running the compiled test.exe
Let the input variables u and z have an observable impact on the printed program output when running the compiled test.exe
Code restructured: User called files are now wrappers of a common, private core function.
Function documentation corrected
Locating template files through the Java CLASSPATH caused problems as long as this project is run. Recent experiments now seem to prove that the ST4 template engine simply doesn't keep its promise to locate and load these files anywhere in the Java CLASSPATH so that configuring this path in Octave is all one needs to do. Instead the ST4 engine tries loading relative file designations only from the startup directory of Octave. As a work around, we now use the Octave search path to locate the f...
Documentation provided: Mainly the Javadoc documentation of the information and services brought to the template expansion process through the new template attribute 'info'
Convenience function added: Template expansion result directly goes to file
Fix: Verbosity had not been set on a per run basis for cached objects
Two new progress messages from the st4Render process degraded to DEBUG. The normal behavior of the script is now restored not to emit anything if nothing particular happens. (Although the definition of log level INFO would allow this, but it may be hindering for the normal, intended, programmatic use of the script)
Octave launch script: More recent typical installation paths entered
Info service is basically working. Template code can emit messages at different severity levels, errors during template compilation and expansion and user emitted errors and warnings are properly counted
Support of Java CLASSPATH control significantly improved by adding scripts to set the dynamic class path and a more transparent launch script for Octave itself. This seems to work well with Octave 4.4
Development branch for integration of the Info object as service provider for the template expansion process. This object is already known from the code generators of the comFramework project and shall be integrated into this project, too
Corrections documentation
Icon file moved into folder doc
Debug code commented out
Many improvements of the documentation.
Typos and corrections
Application logo added
Documentation improved
Documentation extended
More test cases added
More test cases added
Markdwon made compatible with rendering of read...
Documentation of abnormality in Octave's class ...
Missing file added
Useless path removed
Documentation update
Documentation improved.
Minor documentation changes
Home
Many improvements in detail
Many minor improvements, mainly related to docu...
First commit in SourceForge repository; synchro...
Empty folder structure for repository shaped