Keyboard support

On Thu, Feb 16, 2012 at 9:40 PM, karl ramberg <[hidden email]> wrote:
> Works great for me.
>
> I only have Windows so I can't tell if it has platform issues.
>
> Maybe we can mix it with this so the script can be triggered with a
> #keyDown or #keyUp 'event' ?
> http://tracker.squeakland.org/browse/SQ-331
>
> With this the script does not need to be ticking to execute.

The KeyPressMorph could self have a #keyDown and #keyUp script trigger so
it could send messages to other players.

>
> (On second thought I'm not sure if it's a good idea. But it can be
> good to discuss  :-) )
>
> Karl
>
>
> On Thu, Feb 16, 2012 at 9:05 PM, Ricardo Moran <[hidden email]> wrote:
>> Hi,
>>
>> I know this is not in the 16 items list but I made a very simple project to
>> enhance the keyboard support and I would like to get it considered for
>> inclusion. It's based on the suggestions from Bert for my old project in
>> GSoC.
>> It's now a single-key morph and it compares the keyStrings (I don't know if
>> this is good or bad). I hope it works across platforms (even if you have to
>> reconfigure the keys when you open the project). I only have windows here so
>> I would appreciate if someone can tell me if this works on Linux and Mac.
>>
>> Thanks,
>> Richo
>>
>> _______________________________________________
>> etoys-dev mailing list
>> [hidden email]
>> http://lists.squeakland.org/mailman/listinfo/etoys-dev
>>

On Friday 17 Feb 2012 1:35:38 AM Ricardo Moran wrote:
> It's now a single-key morph and it compares the keyStrings (I don't know if
> this is good or bad). I hope it works across platforms (even if you have to
> reconfigure the keys when you open the project). I only have windows here
> so I would appreciate if someone can tell me if this works on Linux and
> Mac.

I tried it on Linux (Kubuntu 10.04). Single and double key presses work as
expected. But third and further keys are ignored (i.e. up+left+right acts as
up+left instead of up).

KeyPressMorph gets my vote. It has awesome implications for interactive
projects on handhelds and smartphone form factors. Thank you, Ricardo.

A few observations:

* apart from just isPressed state, could you also track timePressed? Authors
can use longPress etc. for driving interaction. A key can also be used as an
analog input (e.g. acceleration). Note that isPressed == (timePressed  > 0). 

* If a user presses the button area accidentally, there is no way to escape
out of it. How about clicking the button or the floating tip to cancel the
operation?

* The tip "Press a key" is confusing. Suggest changing it to "Press new key"
or similar and perhaps use blink or color change to indicate modal status.

* The stringmorph "Key:" is superfluous. It comes in the way of grouping keys
into a panel. This could be dropped.

* A new key is not initialized with a label. If a new key is initialized with
'a' label, 'currentKey != nil' becomes invariant. the check for nil in
currentKey could be replaced with an assert or dropped.

HTH .. Subbu

This works great on Windows.
I say it's good to go for inclusion.

Category Scripting ?
Or Just for Fun.

Karl

On Mon, Feb 20, 2012 at 9:28 PM, Ricardo Moran <[hidden email]> wrote:
> I've added all the changes (except the events suggested by karl, which I
> haven't looked at yet). Here is a project for you to test.
>
> If you agree I'll commit this to etoys. The question is: in which category
> should I add the KeyPressMorph? Maybe a new category called
> "Etoys-Keyboard"?
>
> Cheers,
> Richo
>
>
> On Mon, Feb 20, 2012 at 8:59 AM, Bert Freudenberg <[hidden email]>
> wrote:
>>
>> On 20.02.2012, at 00:10, Ricardo Moran wrote:
>>
>> > 2012/2/17 K. K. Subramaniam <[hidden email]>
>> >> I tried it on Linux (Kubuntu 10.04). Single and double key presses work
>> >> as
>> >> expected. But third and further keys are ignored (i.e. up+left+right
>> >> acts as
>> >> up+left instead of up).
>> >>
>> > Yes, that happens to me also (in windows). I think that is a limitation
>> > of the arrow keys, it works when using the WASD keys.
>>
>> It's a limitation of cheap keyboard hardware. Here is a good explanation:
>>
>> http://www.microsoft.com/appliedsciences/antighostingexplained.mspx
>>
>> FWIW, on my Mac keyboard I can press all 4 arrow keys simultaneously and
>> they are all recognized.
>>
>> - Bert -
>>
>> _______________________________________________
>> squeakland mailing list
>> [hidden email]
>> http://lists.squeakland.org/mailman/listinfo/squeakland
>
>
>
> _______________________________________________
> squeakland mailing list
> [hidden email]
> http://lists.squeakland.org/mailman/listinfo/squeakland
>

On Tuesday 21 Feb 2012 1:58:38 AM Ricardo Moran wrote:
> If you agree I'll commit this to etoys. The question is: in which category
> should I add the KeyPressMorph? Maybe a new category called
> "Etoys-Keyboard"?

There are two parts to this extension - one which adds a new morph and another
which adds Etoys tiles to make use of this morph's capabilities. IMHO, the
keypress morph could go into Morphic-Events and the tiles could go into Etoys-
Buttons or into a new generic category (say Etoys-Input).

HTH .. Subbu