Feature #268
Soft keyboard improvements
Added by David Harris almost 14 years ago.
Updated almost 13 years ago.
Description
Thanks very much for Beem :) It's very good.
Feature request:
Various improvements for soft keyboard users (Xperia X10 here). Specifically,
1. Auto-capitalization; auto-capitalization of words (looks like this can be done in res/layout/chat.xml, adding android:capitalize="sentences" to the EditText entry. At least this is what http://developer.android.com/reference/android/R.styleable.html#EditText implies. I'm not very familiar with Android yet though.)
2. There's some way to make the 'Enter' soft-key used for things like smileys instead. I use SmartKeybaord, and I like this. I can easily put in my most-used smiley (:) and then click the on-screen "Send" button (which already exists). I'm not sure how it's accomplished though. Maybe 'imeOptions="actionSend"' or another imeOption? Maybe setting the AutoCompleteTextView_inputType to textShortMessage? My bet would be the latter, at least of those two.
Thanks again :)
Dave
Files
Sorry, looks like the smiley portion of this request was already covered in Bug #66.
Thanks again,
Dave
- Target version set to 0.1.5
- Tracker changed from Bug to Feature
- Status changed from New to Resolved
- % Done changed from 0 to 100
There is nothing more we can do on this. The rest depends on the InputMethod you use.
- Status changed from Resolved to Closed
Hey, so I took a look into this myself and fixed it. Since you guys are over-riding the default KeyListener (in Chat.java in src/com/beem/project/ui/ ), android:capitalize in the resource xml (chat.xml, chat_compact.xml) won't work.
Instead, you have to add "|textCapSentences" to the <EditText ... android:inputType attribute. In, I suppose, both chat.xml and chat_compact.xml (my phone only and emulator only seem to use chat.xml?). Tested in phone and emulator, works fine.
I also tried to get the soft keyboard to appear automatically. This works on my phone, but I don't have a phone with a hardware keyboard to test this on (clearly if the hard keyboard is open you don't want it to pop up the soft keyboard), so please take this one with a grain of salt. It's also the only Android code I've touched (and probably the most Java I've done in the past year). I've attached a diff.
Thanks,
Dave
P.S.: I'm also not sure if anybody will see the addition to this issue report; if a Beem developer does, can they respond? Otherwise I'll probably try posting to the forum or opening another issue, thinking that this one is dead.
Thanks again,
Dave
- Status changed from Closed to Assigned
- Assignee set to Frédéric Barthéléry
- Target version changed from 0.1.5 to 0.1.6
David Harris wrote:
Hey, so I took a look into this myself and fixed it. Since you guys are over-riding the default KeyListener (in Chat.java in src/com/beem/project/ui/ ), android:capitalize in the resource xml (chat.xml, chat_compact.xml) won't work.
Instead, you have to add "|textCapSentences" to the <EditText ... android:inputType attribute. In, I suppose, both chat.xml and chat_compact.xml (my phone only and emulator only seem to use chat.xml?). Tested in phone and emulator, works fine.
Thanks David, I will try this two method in the evening.
I also tried to get the soft keyboard to appear automatically. This works on my phone, but I don't have a phone with a hardware keyboard to test this on (clearly if the hard keyboard is open you don't want it to pop up the soft keyboard), so please take this one with a grain of salt. It's also the only Android code I've touched (and probably the most Java I've done in the past year). I've attached a diff.
I think most people don't want the soft keyboard to appear automatically because the screen is small and big part of the conversation will be hidden specially in landscape orientation.
Thanks for the quick response Frédéric. I hope the patch works for you - it worked on a few different emulators/phones for me.
As for showing the soft keyboard, I know my preference would be for it to be displayed. But I quite agree that that's not universal and some people would hate it. I wouldn't actually suggest it be done without including an option to control the behaviour, but unfortunately that's beyond my ability at the moment.
Thanks again,
Dave
- Status changed from Assigned to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by