Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Difficult to navigate to/through setup nodes #117

Open
yewang opened this issue Mar 4, 2015 · 2 comments
Open

Difficult to navigate to/through setup nodes #117

yewang opened this issue Mar 4, 2015 · 2 comments
Milestone

Comments

@yewang
Copy link

yewang commented Mar 4, 2015

In viewing the Kogo's Joseki Dictionary (http://www.gliftgo.com/#Kogos), a significant part of the game tree is difficult to access. Directly after the root node, the ninth variation (marked with "I" at 10-3 on the right side) has only setup nodes (nodes that do not have a regular board move, but instead setup properties such as AB, AW, AE) as children. After clicking on I, it does not seem to be possible to progress onto any of those children using just the arrow keys (gui buttons or key presses). However, it seems that using "[" and "]" can invisibly select these setup node children, which can then be progressed onto via the right arrow key.

I guess this is more of a feature request/suggestion to make it easier to discover and navigate to/through setup nodes.

@artasparks
Copy link
Owner

Yes, I agree. Probably I need a to a make a tree viewer for situations like Kogos. But I won't get to it for a little while due other priorities right now.

@yewang
Copy link
Author

yewang commented Mar 13, 2015

A tree viewer would be a nice feature, but there could also be other ways to expose variations and ease navigation.

For example, right now, one issue seems to be that the default next node just isn't set up properly in cases where the children are all setup nodes (I haven't checked if this is also an issue when the children are mixed between moves and setup). However, it seems that "[" and "]" still allows those child setup nodes to be selected and then moved to with the next node (or right arrow key press) button. So, a simple solution to make things a bit easier, would be to just figure out why the default next node is not being set up properly in this situation.

A relatively simple feature that may help in this situation would be the ability to toggle between siblings of the current node (perhaps with up and down arrow buttons/key presses).

Even without a full tree viewer, perhaps the UI could do something to show just a list of children and/or siblings (including empty and setup nodes) of the current node, with the ability to click on this list to navigate to the corresponding node.

@artasparks artasparks added this to the Glift 1.1 milestone Mar 23, 2016
@artasparks artasparks modified the milestones: Glift 1.2, Glift 1.1 May 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants