I had trouble getting it to recognize my "arrow"
The arrow has to be made by starting the head on the left side, drawing back to the center, and ending on the right
$1 Unistroke Recognizer
11–20 of 43 posts
Re: $1 Unistroke Recognizer
#12I wrapped their latest recognizer the $P Point-Cloud Recognizer, as a node.js module here: https://github.com/francoislaberge/outlines Their implementation is quite clean, it really is a nice clean algorithm. It takes reading it to understand the type of shapes (templates) that work best and also as a user how best to draw them. I added a demo that shows you as you draw what it's internal state is and best guess so f…
Very cool. It's interesting that, depending on how I draw it, I get a much higher match for "D" when I draw a box than when I draw a D.
It seems like it might be tricky to train it on what not to recognise. Or maybe you just need a lot of template gestures.
Re: $1 Unistroke Recognizer
#13Drawing anything with a clockwise motion I got a caret.
I think this just recognizes your gestures (i.e. it does not recognize shapes you draw). I added an example of a clockwise triangle (using the site's "Add as example of existing type") and it was then able to recognize clockwise triangles.
Re: $1 Unistroke Recognizer
#14I wonder how the CPU and RAM requirements compare to this: https://en.wikipedia.org/wiki/Graffiti_(Palm_OS)
Back in the day I got quite decent at using that to take notes in class. Was an interesting tool.
Re: $1 Unistroke Recognizer
#15I've played around with this some, and the recognition isn't perfect, but I'm very impressed with how well it can pick up a new pattern from even just one example.
Re: $1 Unistroke Recognizer
#16Also, the following $N multistroke recognizer: https://depts.washington.edu/aimgroup/proj/dollar/ndollar.ht... I built a pretty cool tweak for iOS 5 that integrated it into the operating system: https://www.youtube.com/watch?v=35SX6A9fE0g I haven't thought about it in a long time, but I still think that these gestures could be a great shortcut interface for a multi-touch OS, especially with pressure sensitivity. A de…
My brain can't help but think that we've kinda gone full circle here when simple-stroke gesture recognition is thought of as an interesting new interface idea. I mean, it's been about twenty years since a little app called Graffiti from a little company called Palm gave a brand new way of interfacing with an Apple handheld. Not knocking you at all, because it's a pretty cool app, just commentary on how history repeats itself.
Re: $1 Unistroke Recognizer
#17It would be awesome if someone used this to create a note-taking tool for apple/android smart watches that used the graffiti alphabet: https://en.wikipedia.org/wiki/Graffiti_(Palm_OS)
Re: $1 Unistroke Recognizer
#18If you draw brackets from bottom up they are recorded inverted.
For example, } drawn from bottom up is "recognized" as {.
Re: $1 Unistroke Recognizer
#19It seems (from my experiments) that recognition treats all rotations of objects equally. So for instance it recognizes right bracket as left if drawn backwards. I think there should be a caveat warning there.
I think it's a neat toy, but frankly I don't understand what attracts GUI designers to gestures. They seem lot more complicated than just buttons (even if you would have to push an extra button to get the menu), they are not obvious and you have to learn them to do correctly. Am I missing something?
Re: $1 Unistroke Recognizer
#20I wrapped their latest recognizer the $P Point-Cloud Recognizer, as a node.js module here: https://github.com/francoislaberge/outlines Their implementation is quite clean, it really is a nice clean algorithm. It takes reading it to understand the type of shapes (templates) that work best and also as a user how best to draw them. I added a demo that shows you as you draw what it's internal state is and best guess so f…
Very cool. It's interesting that, depending on how I draw it, I get a much higher match for "D" when I draw a box than when I draw a D. It seems like it might be tricky to train it on what not to recognise. Or maybe you just need a lot of template gestures.
Yeah, I think you really have to design your set of recognized gestures to make them have a low chance of ambiguity.
Hmmm, and yeah you could add templates that are variants of an intended output. To improve the chance of matching important gestures