On Fri, Mar 8, 2013 at 7:00 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br><huge snip><br>
<br>
</div></div>Implement a usable touch-interface for Etoys.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Bert -<br></font></span></blockquote></div><br clear="all"><div>Oh! Heart-strings! Yes, this needs to be done. I can probably even do it... you know I spent a few weeks racking my brain about what if anything I could do to improve Etoys before I sent out the call for ideas, and I drew a blank. One thought I rejected was rebasing it off of Trunk, which I threw out because I know there's already an effort underway, and the scope of the work is more broad than I'm comfortable with.</div>
<div><br></div><div>When I was playing with Etoys on the iPad, one thing I really felt needed to change was the way the keyboard was shown and hidden. I didn't like anything I came up with. I'm nearly convinced that we need a soft keyboard that's implemented in Smalltalk -- it doesn't feel right that this intrinsic part is not made out of the same stuff as everything else -- but that's not a small task. There's a whole dictionary of autocompletion you need, and it has to be fuzzy, to try to guess what the user tried to type based on the probability that it matches a particular term.</div>
<div><br></div><div>I wonder if I could hijack some of the logic from OCompletion/ECompletion.</div><div><br></div><div>I might actually narrow the scope to just the keyboard.</div><div><br></div><div>Either way, this one is definitely in the running. Thanks for the idea, Bert!</div>
<div><br></div>-- <br>Casey Ransberger