Skip to content
Little GolemMake your next move.

new tool for reviewing LG hex games (alternative to trmph)

Public forum discussion.

Hex, Havannah

#51 · lazyplayer

2 Jun 2021

I also would prefer moves ordered in descending order not ascending... right now the game is displayed upside down...

#52 · Tom Ace

3 Jun 2021

Marking is putting bookmarks at pages of a book.  It lets you come back to key position(s) quickly after playing through a number of variations.

About the two suggestions:  I'm interested to hear what everyone prefers and see if there's any consensus.  The move list order follows the example of trmph.com but I'd be happy to change it if more people would prefer it the other way.

#53 · shalev

3 Jun 2021

Thanks Tom!

I had an unrelated feature request: can we get keyboard shortcuts for all the buttons? I still sometimes use trmph just for the keyboard shortcuts...

#54 · eobllor

3 Jun 2021

A really great tool, thanks (-:

Like Shalev I'd like to have keyboard shortcuts.

Yet another unrelated feature request: would it be possible to add the option to hide the hollow stone that mark the next move when not at the end of a branch? I sometimes find it slightly confusing when reviewing a game.

#55 · Tom Ace

3 Jun 2021

Thanks for the suggestion to add keyboard shortcuts.  I coded this today but I'm interested to know which shortcuts people want before releasing it.  For now I implemented the same four that trmph has: n,p,l,f for next, prev, last, first.  Also, I have the left+right arrow keys set to prev+next, and the down+up arrow keys to br<— and —>br .  My preference is to not have keyboard shortcuts for actions that change things (delete, set advantage, ...) because it's easy to hit keys by mistake.  Please let me know what you think.

Also, interesting suggestion to optionally disable hollow stones.  It's easy so I'll do it.

#56 · Arek Kulczycki

4 Jun 2021

Amazing job Tom!

I also have one request if I may, pls make the UI elements not selectable, I guess something like user-select: none;

I keep involuntarily selecting something.

#57 · Tom Ace

4 Jun 2021

Arek:  "user-select: none;" does fix this and I will put it in the next release.  I don't do much work in HTML so I don't know all the tricks.  Thanks very much for telling me about this!

#59 · lazyplayer

5 Jun 2021

Tom, now I understand and marking is in fact the proposed solution for my problem. I should mark my preferred position and then the forward button will pick that. Correct? Well then I would recommend we have two buttons, "next mark" and "previous mark", instead of a single button for "going to the mark". I would also change "mark" to "preferred" or something like that.

But in all honesty this is not exactly right, because there could be two positions, so that in one position the "marked" position is the "right" successor and in the other it isn't. Maybe the proper solution is to extend the minmax concept into more levels, large advantage, medium advantage small advantage, and then link forward button to the largest advantage? If there are multiple moves with the same advantage then forward button should probably be disabled because there is no right way to continue.

#60 · lazyplayer

5 Jun 2021

Maybe you can have a counter for evaluation and then when we click "black advantage" the counter is decremented, and white advantage it's incremented. Zero indicates "balance".

#61 · shalev

5 Jun 2021

Tom, I would prefer keyboard shortcuts even for "delete" and "set advantage", since I use them fairly often. Maybe something that uses a second key, like shift+D or control+D?

#62 · Arek Kulczycki

7 Jun 2021

Tom, another thing. Maybe I am missing something, but usually after investigating a branch I forget to set advantage on the leaves. Later I cannot set advantage to the whole branch because there are already branches inside. Is that something you could implement, to propagate the advantage to all child branches?

#63 · David J Bush

7 Jun 2021

If you do not set the advantage on a leaf node, then the next move symbol would indicate that, would it not?

How difficult is it to search your tree for unresolved leaves?

If you do not remember which leaf you did not mark, look at all of them.

If you don't remember, how do you know that you did not miss some branch with the opposite outcome?

#64 · Tom Ace

8 Jun 2021

I don't want to support multiple levels of advantage.  I used jhex a lot and never used the two levels that it has.

For several reasons (including the points mentioned by David), I prefer to only allow advantage setting on leaves.

shalev has convinced me to add a shortcut for delete and set advantage.  I'm not sure yet if it'll be ctrl- or just plain.

#65 · lazyplayer

8 Jun 2021

Tom, so you don't want to mark internal nodes with advantage but you're willing to mark them with "preferred"? I think that you're inconsistent. :)

#66 · lazyplayer

8 Jun 2021

Anyway, more seriously, without multi levels of advantage t some point we've to stop analysing because we can no longer remember what was closer to winning and what was not. I can live without a principled "forward" button but I can't live without knowing what is worth looking again and what is not.

#67 · lazyplayer

8 Jun 2021

Btw, what is licensing of the code? If you are OK with it I can considering forking a new version with the multiple levels

#68 · lazyplayer

8 Jun 2021

Another missing feature, but very hard to implement, is some sort of equivalence between positions. In hex there are often many moves that, after you look at them, you see that they're equivalent, or nearly so. You would like to link or merge the two trees but you can't because they're theoretically different moves... well, perfection is not of this world...

#69 · David J Bush

8 Jun 2021

Lazy, if an analysis tool can recognize common patterns, that sounds the same to me as an engine, something that can figure out aspects of the game which the user did not necessarily figure out. As such, I would call that unethical.

#70 · lazyplayer

9 Jun 2021

David, the idea would be to insert the pattern, that is, to insert the fact that two positions are equivalent. But yeah the more feature this thing has the more "computer-assisted". Is this bad? Not necessarily. As long as we all play by the same rules there is no unfairness.

#71 · Arek Kulczycki

10 Jun 2021

Hmm, seems you've got it worked out then. I don't really exploit all the options the tool provides, I just click a lot very fast and later regret that things aren't marked... So conveniently I would mark the root of analysis as won/lost if I already made my mind, but if there are drawbacks to that then all good :)

#72 · add3993

12 Jun 2021

Yeah lazy's suggestion seems solid.  Basically I think you're asking for, in addition to "advantage white/advantage black" labels for game-tree nodes, a collection of extra labels (A, B, C...)

when you use label A you're marking that as similar to other things you've marked A, but otherwise agnostic to its game value.  It could refer e.g. to a local outcome on part of the board.

#73 · lazyplayer

13 Jun 2021

add3993, yeah you can see it like that, but it would require marking internal nodes, and that was already discarded... well, it's not possible to make everyone happy with the same tool.

#74 · lazyplayer

13 Jun 2021

The tool would also have to deal with inconsistencies, like, two nodes are marked the same, but one seems winning and the other losing. In general when you mark internal nodes you get these inconsistencies and indeed they're a problem.

#75 · Tom Ace

28 Jun 2021

I uploaded a new version (2.4) today.  It has the option to disable rings (hollow stones) as requested by eobllor.  It has keyboard shortcuts as requested by shalev and eobllor.  It disables selecting images as requested by Arek Kulczycki.

The documentation (click help in the drop-down menu) has the details.

A funny thing happened when I coded keyboard shortcuts.  They worked in every browser I tried except Firefox, which has a bug that makes keystroke events stop working in some situations.  I went to report the bug and found that someone else had already reported it, ten years ago. https://bugzilla.mozilla.org/show_bug.cgi?id=706773  I've seen browser bugs languish for a while before, but leaving a bug unfixed for ten years is impressive.  I recoded a few things to work around Firefox's bug and now it works in every browser I have on hand.

As usual, let me know if you find any problems.

#77 · shalev

3 Jul 2021

Thanks Tom!

This is just a nitpick at this point, but "command + left-arrow" now goes back a move, whereas I use that shortcut to navigate back to the previous page in the browser. So if I want to quickly analyze a move from littlegolem, I would click on the minortriad link, click a few moves, then click "command + left-arrow" to return to littlegolem, but that will fail and I'd have to reach for the mouse to click the back arrow in the corner of the screen.

Is there a way for you to bind "leftarrow" as a keyboard shortcut, but not to also steal "command + leftarrow" which is a browser shortcut? I'm using Chrome on a mac.

#78 · Tom Ace

6 Jul 2021

I uploaded a new release today (2.5).  It has minor bug fixes and it preserves the function of command+leftarrow.  Thanks to shalev for the request and for his help with testing.

#79 · Tom Ace

20 Dec 2021

I'm thinking about supporting two levels of advantage. I started with only one level because I like a simple user interface (not a lot of buttons) and I never felt a need for multiple levels when I've analyzed games myself. I recognize that some people would like more than one level but I don't know how many people would use the feature if it were there. Would you?

My preference is to disrupt the existing look and feel as little as possible. I would like to continue using + and - in stones to indicate advantage and disadvantage. Two levels could be indicated with hollow and solid - and + symbols. It seems intuitive to me that hollow means weak and solid means strong; do you agree?

sample

I'd like to keep just two buttons -- adv. w and adv. b -- but there are several ways to have them operate, e.g.:

  1. clicking cycles through levels: the first click on an adv button sets weak; clicking again increases to strong; clicking yet again returns to neutral.
  2. click sets weak advantage, ctrl-click sets strong advantage.
  3. click sets strong advantage, ctrl-click sets weak advantage.
  4. [feel free to offer another suggestion]

Each method has pros and cons. If weak advantage is indicated by hollow + and strong advantage by solid +, methods 1 and 2 would not preserve the existing look and feel for players who only want to set one level of advantage. You'd be seeing hollow symbols all the time instead of filled ones, which I personally would find somewhat irksome.

Then there's the question of how keyboard shortcuts should work.

#81 · David J Bush

20 Dec 2021

I'm all in favor of five possible labels (including unevaluated) for next move symbols. Thanks.

#82 · lazyplayer

29 Dec 2021

Tom, thanks for the improvement. I do have an aesthetic complain. The white stones don't have the ring in them. They're not symmetrical with black. This greatly diminishes the beauty of everything heh. :)

#83 · Tom Ace

16 Jun 2022

I have a new version that supports two levels of advantage (advantage or "½ advantage" for either black or white). It's available as a beta version for testing at https://minortriad.com/ahexlgbeta.html

The new ½ advantage feature is optional (you can disable it in the menu that comes up when you click on the ☰ icon). Files written with this beta version that contain ½ advantage positions won't be readable by earlier versions.

Comments, suggestions, and bug reports are welcome.

Last page