Posted: Thu Jun 09, 2016 5:19 pm
Pattern recognition may be difficult.
We'd probably call this a block:
We'd probably call this a block:
Life in 19x19. Go, Weiqi, Baduk... Thats the life.
https://www.lifein19x19.com/
"Stretch" is used in the Level Up books. I don't know if it's more generally used in translations of Korean books. I too am more used to "extend" and "descend".EdLee wrote: (*) Some of the terms displayed are unusual.
Example: 'Stretch' -- usually, we use 'extend' ( or 'descend' or 'drop' for certain cases; and others ).
Example: 'Attachment' -- unusual -- usually, we see 'attach' in books, or game commentaries, etc.
I see. I find a toolbar only clutters the interface while the features can be as easily accessed through the menus. Toolbars have fallen out of favor in UI design recently. I think this is out of the scope at the moment.EdLee wrote:Not the OS Text menus. But a Buttons menu; example:
Alt+C is bad because it overrides the Windows internal menu mnemonic shortcuts. I've never encountered any native applications that uses single letter shortcuts. Surely you want to turn on coordinates when writing reviews without having to focus the board first. Speaking of bad shortcuts, I should probably stop using 'Ctrl+Alt+' shortcuts, as it has special meaning on Windows.EdLee wrote:gIgo used Alt+C to toggle coordinates, which I find a little awkward. Go Panda uses the single letter 'c' directly (if the hotspot is the board).
Some questions arise when implementing this:EdLee wrote:It may make no sense to you, but it makes a lot of sense to some other people.yishn wrote:When navigating the SGF file, there won't be a stone click sound, as it makes no sense.Currently, when I replay an existing SGF, there is no stone click sound on each move --
could this be an option ?
I'm sure you have. However, Sabaki is a reimagination of a SGF editor for the modern world without any preconceptions. We should think through before making decisions and avoid blindly copying behavior or features from those who came before.EdLee wrote: These are all feedback from a Go apps user of 14+ years.
Hi yishn, I disagree. I've added more to post 56; your metaphor is also incomplete.yishn wrote:Using this metaphor, you should only hear a sound if you actively click/touch the board. That is the most natural solution: To play no sounds when navigating.
I agree, and I assure you I'm not blindly providing any feedback to you.We should think through before making decisions and avoid blindly copying behavior or features from those who came before.
Too intuitively obvious; not a point.What about navigating one step back? Should there be a sound for that? Probably not, but why is it that only forward movement has sound?
MultiGo, SmartGo, and Wbaduk (and possibly other apps) have the option of stone sounds on replay.There is a slider, you can slide from move 0 to move 100 in one second. How many times should the click sound be played?...
MultiGo handles this...
No, it's not inconsistent. Just think YouTube slider: it's a solved problem. There's no problem here.Sabaki also plays capture sounds. Should these play for skimming up and down? If yes, it doesn't make sense metaphor-wise, if no, highly inconsistent.
You can replay games by clicking on the board, on the position where the next stone lies. There will be sound. I'm well aware you only want an option. My point is, I don't see a way to implement this right.EdLee wrote:Hi yishn, I disagree. I've added more to post 56; your metaphor is also incomplete.yishn wrote:Using this metaphor, you should only hear a sound if you actively click/touch the board. That is the most natural solution: To play no sounds when navigating.
In any case, it's only a request for an Option.
You didn't respond to my objection to MultiGo's sound handling. MultiGo has not solved this problem in a way that's good enough for me. As for how SmartGo handles this problem, I have no idea. Also at least MultiGo doesn't have capture sounds.Both MultiGo and SmartGo (and possibly other editors) have the option of stone sounds on replay.
I don't think this is a big issue: if the replay speed exceeds a certain threshold, no sound.
I really don't see how the YouTube slider can solve this problem, please enlighten me. Skimming also include pressing the down key for a longer period of time. Or clicking and holding the down button on the slider. Or using the mouse wheel.No, it's not inconsistent. Just think YouTube slider: it's a solved problem. There's no problem here.Sabaki also plays capture sounds. Should these play for skimming up and down? If yes, it doesn't make sense metaphor-wise, if no, highly inconsistent.
You need to specify the path to Leela as an argument, i.e:pleiade67 wrote: /opt/local/bin/wine /Users/pleiade/Library/Go-engine-win/Leela/Leela070/Leela070GTP/Leela070GTP.exe
with argument: --gtp
is not interpreted by Sabaki (and gives a connection error), whereas Gogui interprets the same command and launches Leela as expected.
The working directory for the engine is the directory specified in path. That means in the case above, the working directory is /opt/local/bin.pleiade67 wrote: Another question is the definition of a working directory for the engine (some engines require an existing working directory).
That is an interesting idea. I've created an issue regarding this.Koosh wrote: Feedback 1
The one editing feature I'd like to see is the ability to cut/copy and paste lines along the game tree. When I'm recording, I might make a mistake inputting a sequence of several moves and then realize I put it into the wrong variation branch.
The only way I can do this (I've found) is to manually edit the text of the SGF file.
The problem is that one can scroll very fast through the game. Updating the board is fast, but updating the game graph is quite expensive, especially if the file you opened happens to be Kogo's Joseki Dictionary. Therefore, Sabaki only updates the graph once the user stops navigating. Maybe I can try to reduce the lag.Koosh wrote: Feedback 2
When you scroll through games, there is a disconnect between what is shown on the board and what position you are at along the game tree. It takes about a second to update the position on the tree when you stop scrolling. When scrolling 20 moves, for example, I have to stop and check where I am in the tree before continuing.
It would be nice if this lag was not there and the tree updated as you scrolled along it.
How about being cleverer about when to update: if you know the game record is small (e.g. the sgf is under 5kb which should cover most game records, or count the nodes) then try to update the game tree immediately, but delay for big files?yishn wrote: The problem is that one can scroll very fast through the game. Updating the board is fast, but updating the game graph is quite expensive, especially if the file you opened happens to be Kogo's Joseki Dictionary. Therefore, Sabaki only updates the graph once the user stops navigating. Maybe I can try to reduce the lag.