Artemis Sparks
Artemis Sparks
Right now the mark generation lives in glift.displays.board. For ease of reuse for diagrams, it would be nice to move it to the svg lib.
For ease of use, the SVG code should be moved out of displays. It doesn't necessarily need to be used for glift display, for example.
For long SGF Collections, it would be nice to be able to jump to problem / page. The most logical way to support this would be to turn the page-icon...
It would be great if Glift supported MarkDown commentary. Markdown has the added advantage of looking decent even when it isn't rendered (except, maybe, for URLs).
The tooltip implementation is really jenky and obviously less than ideal. The tooltips don't hover over the right elements and, moreover, the are obscured when in fullscreen mode.
One of the big feature requests I've heard is to hide the comment-box if there are no comments. It's not terribly easy because of the way glift is constructed and...
In movetree-land, we need to have support for deleting properties and for deleting variations
Now that the KGS protocol has been opened up, now is the chance to make Glift work with KGS. The protocol: https://www.gokgs.com/help/protocol.html The mailing list: https://groups.google.com/forum/#!forum/kgs-client-coding