Extract components into separate modules

[ehq]

Hey!

I love this project and it looks amazing, so I just have a small suggestion that would be great for my use case. I'm developing http://goban.co and I already have my own visual board implementation which uses canvas and it's customized with the specific features I need.

I would really love to use the kifu JSON standard proposed in this project though, as well as the sgf parser. The problem for me is that it's not very easy to extract those components and re use them in my project, and I have no need of the html player provided here.

If we could have a way to separate the visual board from the backend game logic I think this library would be more flexible and cover more use cases.

[waltheri]

Hello,

first of all I am glad you like it. I tried to design WGo to be flexible and extensible, however graphical board and game logic component are essentially the library. Player itself is only extension of WGo, as well SGF parser.

On the other side, I think that separation of individual components shouldn't be so difficult. For example: for the sgf parser and JSON format you need classes KNode, Kifu and few functions from the file kifu.js, then you need whole file sgfparser.js, in the end you need simple WGo container:

WGo = {};

And that should do it.

If you would have any suggestion to improve WGo library, let me know. And thanks for feedback.