Fri, 21 Jul 2017 11:39:30 +0200 version 1.4.9 jv
Patrik Svestka <patrik.svestka@gmail.com> [Fri, 21 Jul 2017 11:39:30 +0200] rev 1517
version 1.4.9 [Batch] Deleting duplicate comments [Batch] Fixing images user_menu - issue with variable expanding, now the images are always listed from newest to oldest (when of the same age name sorting is done) There was a CALL (function) collision with variable name (user_input) -> function renamed to :user_menu. Variables were renamed to be clear when somebody else would be reading it. Added new section to get path and file name from the the user's answer (with error handling).
Thu, 20 Jul 2017 12:35:09 +0200 version 1.4.8 jv
Patrik Svestka <patrik.svestka@gmail.com> [Thu, 20 Jul 2017 12:35:09 +0200] rev 1516
version 1.4.8 [Batch] Adding error handling when doing the variable expansion from the configuration file from the path variables [Batch] Improving the stx.log_suffix adding of encoding prefix - to have the "<prefix>.log" all in double quotes [Batch] Adding new section to the variables' validation to correctly validate if double quotes or backslash is not missing from the variables where the script expects to have them (load them from configuration file) [Batch] Chanding the name stx_bin_dir to stx.stx_bin_dir to indicate that this variable is actually loaded from configuration file [Batch] Improving comments [Batch] Changing the expand function from :expand to :expand_path to better indicate the function and also changed the expansion of %~2 and %~1 to not to expand these variables %2 and %1 (so the path variables still contain the double quotes - thus can have spaces in the path) version 1.4.7 [PS] Better error handling when exiting PowerShell
Tue, 18 Jul 2017 14:00:22 +0200 version 1.4.6 jv
Patrik Svestka <patrik.svestka@gmail.com> [Tue, 18 Jul 2017 14:00:22 +0200] rev 1515
version 1.4.6 [BATCH] printing stdout is done, if possible, via :print_message function [BATCH] when both manual and automatic switches detected - manual wins (--image vs --Ignoreimage) [PS] kicked out the pause when logging is ignored do to locked log file
Wed, 12 Jul 2017 10:25:43 +0200 Windows launcher improvement - starting is still done via smalltalk.bat jv
Patrik Svestka <patrik.svestka@gmail.com> [Wed, 12 Jul 2017 10:25:43 +0200] rev 1514
Windows launcher improvement - starting is still done via smalltalk.bat Part of this release is: smalltalk.bat - main script logging needs a powershell (still possible to run completely without powershell but some features will not be avilable) smalltalk.ps1 - powershell filed called from the smalltalk.bat file to better control log file logging and all the powershell environment smalltalk.cfg - contains configuration for smalltalk.bat and smalltalk.ps1 smalltalk_close_shell.lnk & smalltalk_shell_remains_open.lnk - provided for running withing the project\smalltalk directory, contains custom icon. create_shortcut_on_desktop_via_hardlink.txt - contains guide how to create a desktop shortcut to .lnk files for users via hardlink. ====================================== The features of this advanced script = ====================================== Quick start (with close or leave open the shell after Smalltalk start) Starting with default image on defined path Starting with any image (user is prompted to select one via menu) on defined path Logging into a file - either overwrite or append at start start (minimal PowerShell 2.0 is required) - User can change the log file encoding to ASCII, UTF8 (default), UTF16, UTF32 - User can decide if he wants a date and/or time part added to the log file The script automatically detects PowerShell version and based on that decides which functionality will be available. Error handling on the batch and PowerShell level - user is informed about the details of error Batch file tries to exit gracefully, if possible The advanced features: A warning limit is in place for the log file size. If it gets too large as it may slowdown the Smalltalk. User can decide if there will be a shell opened for error messages or if Smalltalk will for from shell and will not display any messages on the command prompt. User can choose if the validation process is active and if the successful message is shown. User can choose which redirect will be used in PowerShell - if the native one or cmd.exe one (little bit faster in most cases). version 1.4.5 [Batch] Fixed issue with batch string error message (strip the reserved characters. + changed the :exit_sequence function - %~1 to %1 (same with %~2) when calling powershell
Wed, 07 Jun 2017 14:41:35 +0100 Cleanup: Use `UserPreferences class >> loadSettingsFrom:` jv
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 07 Jun 2017 14:41:35 +0100] rev 1513
Cleanup: Use `UserPreferences class >> loadSettingsFrom:` ...or `UserPreferences class >> loadSettings` to load preferences.
Mon, 05 Jun 2017 22:10:20 +0100 UNIX: Added new option `--vdb` to run under Visual / VM Debugger. jv
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 05 Jun 2017 22:10:20 +0100] rev 1512
UNIX: Added new option `--vdb` to run under Visual / VM Debugger.
Thu, 15 Jun 2017 03:59:54 +0000 update tags
convert-repo [Thu, 15 Jun 2017 03:59:54 +0000] rev 1511
update tags
Wed, 14 Jun 2017 15:12:40 +0200 *** empty log message ***
Claus Gittinger <cg@exept.de> [Wed, 14 Jun 2017 15:12:40 +0200] rev 1510
*** empty log message ***
Wed, 14 Jun 2017 15:03:17 +0200 *** empty log message ***
Claus Gittinger <cg@exept.de> [Wed, 14 Jun 2017 15:03:17 +0200] rev 1509
*** empty log message ***
Fri, 02 Jun 2017 22:26:06 +0100 Issue #147: Remove doubled backslash from STX_EXE variable jv
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 02 Jun 2017 22:26:06 +0100] rev 1508
Issue #147: Remove doubled backslash from STX_EXE variable See https://swing.fit.cvut.cz/projects/stx-jv/ticket/147
(0) -1000 -300 -100 -10 +10 +100 tip