Sneak Peek

[Bill Spight]

Congratulations, Mr. D!

Very cool!

[kirkmc]

I see no reason for it to be other than a web app.

After looking a bit more, this is clearly the best joseki tool out there. Congrats!

As for the letters, I'd say they should be a bit bolder, and if you could put shadows around them they might stand out from the board a bit more.

[Li Kao]

I think only variations above a certain probability(say 1%) should get a letter and for the rest just use the same kind of marker to indicate there is a variation at all. Currently it is rather hard to find the most common variations.
And for the ghost stones you might want to use a css tilemap, that way only one (big) image has to be loaded for all of them.

[k1ndofblue]

I think this is very cool also. I look forward to the progress you are making.

On a side note (and I do not even know if it is possible) it would be cool to to see joskis for corners that have had two approch moves played against them.

Thanks!

Use the "pass" button at the bottom and you can do that right now.

That is very awesome! Thanks!

[daniel_the_smith]

I think only variations above a certain probability(say 1%) should get a letter and for the rest just use the same kind of marker to indicate there is a variation at all. Currently it is rather hard to find the most common variations.

Good idea, I might do that.

And for the ghost stones you might want to use a css tilemap, that way only one (big) image has to be loaded for all of them.

Currently there are rather too many of them for that to work (they are generated on the fly by the server), but I will be reducing their number to speed things up anyway. I didn't actually realize you could do that with css, thanks.

[fwiffo]

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: Select all

<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: Select all

.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]

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

[ethanb]

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]

Hmm, do you have an example position?

[Li Kao]

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]

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)

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]

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]

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]

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]

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!