cmd-d us hard on the virtual kdb indeed... As is getting halos to show. I did a bluetooth kbd experiment on iOS but even there one needs hacks to get through. e.g. no escape key... phil Le 10 juin 2013 20:06, "Igor Stasenko" <siguctua@gmail.com> a écrit :
On 10 June 2013 19:59, kilon <thekilon@yahoo.co.uk> wrote:
The question arises whether Pharo should :
a) Use the available virtual keyboard provided by the OS of the mobile device
b) Implement its own
I have pharo on my android device and tries to follow option (a) which is my favorite too. The problem however is that the virtual keyboard provided by option (a) is not a full keyboard and so some pharo shortcuts will not work.
I am not against option (b) either.
i'd vote for both. Having own keyboard has many benefits like staying idendependent from future "overly-clever" keyboards :) Not mentioning, that it can be used on other platforms, which has no virtual keyboard provided by default.
-- View this message in context: http://forum.world.st/Pharo-dev-Virtual-keyboard-tp4692672p4692678.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.