I know. Worst UI ever and no docs. Well at least it doesn't crash much. I just had to get the goddamn thing out. Polish and documentation will come later. It may not be the best way to do it but it's the way I'm doing it.
One big hitch: if you create a new empty grammar, there's no way to get back ot he old one unless you've exported first, and attempting to close at this point causes a hang (win7/64, latest JDK).
A simple link to the source material you're working with for the grammar concepts would go a long way towards fixing the documentation gap in the meantime.
There isn't any source material. I do have some minimal docs on google code : https://code.google.com/p/fleen/
Actually, this really confuses me. Aside from the single letters, the UI is actually very soft and pretty in a way. What compelled you to not use full words?
http://glowinggreenhand.blogspot.com/2014/02/fleen-quasar-in...
Besides the UX issue of not being able to return from an empty grammar, a few small things I've noticed: * Is there a reason for leaving empty padding around the bounds of the generated PNG's * Vector export doesn't seem to work (I tried by having it set as the only selection as well as having it in addition to the PNG option)
I put the padding around the exported PNGs because sometimes a bit of stroke can overlap the edge of the image so I wanted some wiggle room. One of many temporary shortcuts in the design to be cleaned up later.
Going viral long after launch (and many revisions) is always possible. Best recent example: flappy bird.