Hi again Sydnal,
sydnal wrote:
> @ Jonas;
>
> Well I guess it can be considered a shame on my part that I did not
> know about xstroke before your post. Anyway I examined the link,
> however the way strokes are defined is somewhat different. Xstroke
> seems to define strokes using regions which it passes through, DKN
> uses a list of sample points that lie on strokes path. (Well they are
> the same thing as the number of regions increase i guess) You can,
> though, implement any stroke as easily. Just define a path for your
> stroke as a list of points, e.g. { P(0,0), P(0,1) } would be a
> downward stroke.
True, the interesting thing about xstroke's approach is that it is very
compact (so easy to extend) and uses regular expressions to allow
alternative ways to define each character. The drawback is that the 9
regions may be a limitation for complex characters.
> I am in no way an expert on designing a public API so I am sure sure
> its current state is far from optimal. I'll try to get a google code
> site going for it when / if i get the time. Thanks for your response.
I'd be interested in looking deeper into this when you are ready. I find
this way of entering characters more reliable than an virtual keyboard
on the touch screen - maybe my fingers are just to fat... ;-)
Best / Jonas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
