Sneak Peek

fwiffo · **#21**

Actually, you don't need separate images for different levels of transparency. Just use the black stone and white stone images, and set the transparency with CSS.

First, calculate the following:
Bo = (games with a black stone)/(games with any stone)
Wo = (games with any stone)/(total number of games games)

The markup would look something like:

Code:

<div class="wstone" style="opacity: Wo;"><div class="bstone" style="opacity: Bo;"></div></div>

Substituting Bo and Wo.

The the base stylesheet would be something like:

Code:

.wstone, .bstone {
    width: 26px;
    height: 26px;
}

.wstone {
    background: transparent url(images/wstone.png);
}

.bstone {
    background: transparent url(images/bstone.png);
}

Of course, to get cross-browser compatibility you'll have to add some browser-specific styles (e.g. using filter: in IE6 and IE7 and -moz-opacity for older versions of Firefox, etc.)

daniel_the_smith · **#22**

Wow, thanks fwiffo, that will speed it up a lot!!

ethanb · **#23**

Why do the ghost stones disappear when there is only one path? It seems like that's almost when they would be the most useful!

But the site as a whole is a really neat idea! I like it!

daniel_the_smith · **#24**

Hmm, do you have an example position?

Li Kao · **#25**

The way you keep state is broken. If you open two instances of the website they interfere.
And I think each position should have a unique url. If you want to use the position id only from JS it is a good idea to put it behind a # mark, since this doesn't cause a page reload.

daniel_the_smith · **#26**

The site was down for a bit earlier. I started it up again. I know what's wrong and will fix it tonight. (Thanks, loki, for pointing that out after my game with Actorios)

Li Kao wrote:

The way you keep state is broken. If you open two instances of the website they interfere.
And I think each position should have a unique url. If you want to use the position id only from JS it is a good idea to put it behind a # mark, since this doesn't cause a page reload.

I agree the state keeping is not ideal, but it's a ways down on my list.

The words "This position" are a link to a URL that will take you to the position, e.g., low distant approach to 3-4. Is that good enough or were you looking for something else?

Li Kao · **#27**

yes, exactly that. I'd like the url to point to the current position is some way(probably using http://dailyjoseki.com/browse#bxkwvabvu)

daniel_the_smith · **#28**

So you're asking for the URL you see in the address bar to change with every click? I might be able to pull that off with the # syntax. But this also will probably not be at the top of the list for a while.

Li Kao · **#29**

Another idea:
Show when the current variation was first/last played. Perhaps display a histogram showing its popularity over time.

btw what programming language are you using?

daniel_the_smith · **#30**

Li Kao wrote:

Another idea:
Show when the current variation was first/last played. Perhaps display a histogram showing its popularity over time.

btw what programming language are you using?

Been waiting for someone to ask that, I'm using this awesome new language. Both for the server, and for the utility that builds the tree. For a database, I'm using mongodb, although the browse page doesn't need the database.

Yeah, how recent a joseki is is something I intend to incorporate eventually. A histogram would be a nice touch!

Li Kao · **#31**

Golang is an interesting language. I read a bit about it when it was first published.
My memory is a bit muddy, but there were a few things I found strange then. Something about value-types vs reference-types, something about lack of generics requiring unnecessary casts and something about user defined types being inferior to built in types.

daniel_the_smith · **#32**

daniel_the_smith wrote:

The site was down for a bit earlier. I started it up again. I know what's wrong and will fix it tonight. (Thanks, loki, for pointing that out after my game with Actorios)

OK, I added some panic protection (in addition to fixing the bug [*]), so it shouldn't go down like that again. Since it was just me until yesterday I wanted it to crash when something unexpected happened, I forgot to change things before announcing it.

Now I'm kinda hoping you can crash it so I can see my fancy call stack report in the log... :twisted:

[*] So now you can attempt to get a directory listing from /image/ without taking down the server, whoever you were

wineandgolover · **#33**

Daniel,

This is very impressive. Well done.

The first upgrade I would recommend is filters. Examples include "date range" "country" and "player". For example, this would be a great way to determine how the Koreans are currently answering the one space high approach pincer, rather than seeing a percentage that includes potentially obsolete joseki.

Also, I am a bit slow and am not sure I 100% understand how the surrounding positions works. Let's say that in a joseki played 100 times, the opposite starpoint was black 25 times, white 25 times, and empty 50 times. How would that display? If it was 50 black and 50 white, would it look the same? 50 white and 50 empty? 75 white, 25 empty?

I am sure this would be hard, but it would be cool if you could hover your pointer over a ghost stone and it would tell you, "black 25%, white 25%, empty 50%.

Will your db update as GoGod updates?

Thanks for sharing. Let me know if you need a beta tester for future features.

I'll keep playing with it and let you know if I have other ideas.

See you at the congress.

Again, great job!

-Brady

wineandgolover · **#34**

Another question - it seem the position determination is color independent, is this correct? ("This position was reached x time(s)")

And another idea of dubious value, but some interest: include "Black Winning Percentage" with each variation.

daniel_the_smith · **#35**

I've implemented the opacity & sprite suggestions. Safari (on my iPad) shows the sprites a pixel off, does anyone know anything about that? Firefox, chrome, and opera all display it correctly. I don't have a convenient way to test on IE or Safari (on a mac). I don't think I'll update the main site quite until I figure out what's wrong with Safari.

The updated version is running at http://dailyjoseki.com:30080/browse if you want to take a look. Not sure how long I'll leave it up.

daniel_the_smith · **#36**

wineandgolover wrote:

The first upgrade I would recommend is filters. Examples include "date range" "country" and "player". For example, this would be a great way to determine how the Koreans are currently answering the one space high approach pincer, rather than seeing a percentage that includes potentially obsolete joseki.

Yeah, I agree it would be interesting. Filtering by date, especially. Filtering the joseki tree isn't too hard, I don't think, but the average board feature makes it tricky. It's on my list.

wineandgolover wrote:

Also, I am a bit slow and am not sure I 100% understand how the surrounding positions works. Let's say that in a joseki played 100 times, the opposite starpoint was black 25 times, white 25 times, and empty 50 times. How would that display? If it was 50 black and 50 white, would it look the same? 50 white and 50 empty? 75 white, 25 empty?

How transparent it is depends on how often there was a stone there at all, the color depends on what color the stone was. So, if it's black 25 times and white 25 times out of 100, it would be 50% transparent grey. 50 B and 50 W, it would be 100% opaque grey. 50 W and 50 empty, it would be 50% transparent and white. Etc.

wineandgolover wrote:

I am sure this would be hard, but it would be cool if you could hover your pointer over a ghost stone and it would tell you, "black 25%, white 25%, empty 50%.

Actually, I set the alt property, so it should be doing that already with a tool-tip. But it's making it look terrible while loading, so I'm turning it off...

wineandgolover wrote:

Will your db update as GoGod updates?

Yeah, I hear there's 3000 more games in the upcoming edition, which I'll add sometime after I get it.

wineandgolover wrote:

Another question - it seem the position determination is color independent, is this correct? ("This position was reached x time(s)")

And another idea of dubious value, but some interest: include "Black Winning Percentage" with each variation.

Yes, positions can be reached several ways. Color, rotation, mirroring, side to play are all appropriately dealt with. Which reminds me: the "tenuki" count is incorrect for positions that can be reached in multiple ways, it combines black tenukis and white tenukis. Next time I feel like working on the tree I will fix this.

Winning percentage would be fun. Maybe I'll add it if it's easy to parse the info out of GoGoD files (I haven't checked).

Anyway, thanks for checking it out, glad you like it

John Fairbairn · **#37**

I would have preferred that Daniel made this clear himself, but can I just mention that GoGoD has indeed given permission in principle. Daniel and T Mark will iron out the details at the US Congress, but the general thrust is that we will expect a restriction on the number of moves per game made available, and also on the amount of header data supplied.

We welcome creative uses of our database. We have alreaady given similar permission to quite a range of people, companies and academic institutions and (I think - T Mark can confirm) we have never charged. But in return we do expect some sensible restrictions, and all the features requested here must go through that filter.

lorill · **#38**

daniel_the_smith wrote:

Actually, I set the alt property, so it should be doing that already with a tool-tip. But it's making it look terrible while loading, so I'm turning it off...

Use title for tooltips instead of alt.

ethanb · **#39**

daniel_the_smith wrote:

Hmm, do you have an example position?

Assuming that's addressed to my question about the ghost stones, it happens on anything where there's only one path (no matter how many times it was played.)

I found it browsing through taisha variations - one pattern was played with minor variations in only 3 games, but in places where all the "next moves" were the same move, or if I went to a track with only one game, the ghost stones weren't rendered.

CarlJung · **#40**

Put link in sig.

Sneak Peek

Who is online