pkglint -Wall -r --autofix --only aligned
After running the above command, three packages had to be adjusted
manually:
In maelstrom-x11, pkglint didn't see that a commented variable
assignment should have been re-aligned as well.
In netmaze, there was a single line that didn't align well with all the
others, but pkglint decided to adjust the whole paragraph to this single
line. The result would have been ok, but not good.
In tscp, there was a paragraph where some of the lines were indented
one space more than the others. This rule is useful when one variable
name is very long compared to the others, but not in this case.
Version 2.3.0 (feb.18th 2015)
New features:
* Grinder can now find the CA[] property (ChAracter set, e.g. "CA[big5]") in
the sgf and decode the file appropriate. However, some decodings are not
supported by Java, e.g. HZ / CA[hz-gb-2312] / ~{NbGeT49mJV~}
* When reading a file with no "CA[]" property set, we use the default of the
jvm to read the sgf (this was and is the default behaviour). You can set
a different character set as preferred default in the settings window.
The selection of a default decoding (settings) helps decoding files, if
MyGoGrinder is used in portable mode on different OSs: Linux and Mac
usually use UTF-8, while Windows uses the local decoding/encoding.
* If comments of sgf files are not displayed correctly, you can set the
decoding manually: you can switch the decoding ("View" menu -> "Change
text decoding") and you can also set this for all files of the current
folder - without subdirectories (Grinder will remember this).
* The settings file (mygrinder.ini) is now saved and read always with UTF-8
encoding, so that it doesn't matter which default decoding the machine
uses.
* Log files are now also always written with UTF-8 encoding, so that
messages with Russian, Chinese, Hebrew and Inuktitut characters can be
read side by side with Latin (ASCII) characters. The old logs and
settings are backed up.
* When importing tags from a file, you can select the decoding.
* You can let Grinder automatically move defect and unusable files to the
folders "defect" resp. "notsupported"; activate this manually in the
settings file (mygrinder.ini)! This will deactivate editing of defect
files.
* Changed display order of directories in the selection window: Java's file
lists were not sorted, when got from some file system: FAT32 (thumb
drive), ext4 (Linux). NTFS file systems gave an ordered list, so
possibly you didn't ever observe this. You can switch sorted display
off, if you liked the old unsorted list.
* If you want to use the wgf editor, you need to activate it's main window's
menue entry manually in the settings file: WGFFRAME.ENABLED=true
I took the check box out of the settings window.
Tweaks, bug fixes:
* I reduced the count of warning messages, if starting a new profile.
* "\" and "]" are now also handled correctly in the comment area of the main
window
* If there is an error in the sgf code or the file was not found (moved or
deleted), instead of "Exit" we use now a default code, so that the
program can continue normally.
* Refresh the directories view in the selection window without closing the
program
* While working on the code, I remembered a behaviour in Linux: if you make
a soft link to an external problems collection in your problems folder,
these problems are used as if they were inside your problems folder. So
stats files are created (but defect files cannot be moved). This doesn't
work in Windows!
* Sometimes, when deleting a tag in the selection window, the tags list was
suddenly empty (shock). This was just a refresh-display-problem -
seemingly solved
* I threw the MYGG_DEBUG... system variables out.
* ... and some more small tweaks and fixes, which I don't remember
Version 2.2.0 (DECEMBER 2014)
Bugs fixed:
* The WGF-editor didn't take the new board size in some circumstances
(introduced with the work on the parser)- repaired
* play stone was also registered on the invisible part of the board (already
in 1.02)
* Splash screen: was too much white - repaired
Bug or feature?:
* When the "Apply Tag..." button has the focus, a key pressed sets the tag
with this first letter, so key "c" or "C" would set "Corner" but if you
type "cu", the code would set "Corner" AND "Cut"! This is not clean, as
you would need to delete "Corner", if this isn't wanted. This is an old
"feature": I found it also in version 1.02
Further:
* PathToSettings can now be set by environment variable (path needs to exist
and be write enabled) - so you can have a 2nd, 3rd etc. profile for
the same user
* Environment variable: same goes with toggle stacktrace on for SGF-errors
and set path to doc (help files)
--> see SysVariables.txt
* The same with log level for SGF errors (0-3, default is 1)
--> see SysVariables.txt
* Grinder can now recognize the location of the program's .jar file (usually
it expects the help files in the program's subdirectory "doc" - this was
a problem, when Grinder was started with a desktop script, which didn't
cd to Grinder's program folder before)
* Startup: shortened the display of the scanned path - now it fits better in
the splash screen
* Error messages concerning SGF code: they can now show the affected code
and highlight it (loglevel 2 and 3)
* DEMO.WGF moved to doc folder (where the help files reside) (Grinder tries
to find it there, but falls back to load it from the program's folder)
* File size is now restricted to files with up to ~100kby (default); this
can be overridden in the settings file or with setting a system variable
--> see SysVariables.txt
* Set some system variables to control the behaviour of the program:
MYGG_DOCPATH, MYGG_SETTINGS, MYGG_LOG_LVL,
MYGG_SGF_MAX_SZ (and some more)
* you get a warning, if one of the log files grows too big (default is ~1mby,
change that in the settings file)
* I thought, that the price for my works in the parser is more time
consumption when parsing. I did a small test with ~1000 files, one time
with GoGrinder 1.14, one time with MyGoGrinder 2.1.1: nothing remarkable!
both needed around 45 seconds!
* Portable - use the command line switch -p or -portable to run Grinder with
sgf and settings in Grinder's program folder: this still needs some
polishing: switching to the next problem takes too long.
Version 2.1.0 (oct.29th 2014)
Bugs fixed:
* The switch -sysinfo worked only in Windows - in Linux (?also in Mac?) the
clipboard is deleted on exit
* extensive work in the SGF-parser, "\" and "]" are handled correct IN THE
PARSER (not yet in the display)
Further:
* SGF FF[3] files (AddWhite, SiZe, DaTe, CiRcle, ...) are now processed and
displayed!!
* Files from a defect version of Hibiscus 2.1 (LB[yy:0]...) are now displayed
* Many defect SGF files get now a suitable error message; a stacktrace is
only shown for debugging (internal switch "DEBUG2"). Normal file errors
shouldn't give a stack trace. (If you have a defect sgf file, which
doesn't get an sppropriate error message - let me know!)
* Grinder has now an extra log file for SGF file errors: sgf-log.txt
Version 2.0.3 (sept.2nd 2014)
Bugs fixed:
* corrected command line help und command line sysinfo
* save wgf file was defect since several weeks
* split sgf (with more than one problem) was defect (since v.2.0)
Version 2.0.2 (aug.26th 2014)
Bugs fixed:
* Test/start editor uses now the editor's program directory as working directory
* When a program's path is handed over from the file selection window, and the
path for the executable contains spaces: encase the path with quotation marks
* When at first startup a "default.sgf" is written, it has now (;GM[1]... as GaMe type
GM[0] is wrong and impossible (CGoban gave me the hint)
Version 2.0.1 (aug.20th 2014)
Bugs fixed:
* The Mac resize thing doesn't anymore look ugly
(but still: if you close the program with apple-q, it doesn't save settings)
* Set default language by command line switch works now as planned
* Repaired a bug in the settings window
Further:
* One .jar file for both Java 5 and Java 6+
* Validate files works now better, but you still get a long stack trace for every defect file
* some small corrections
