![]() |
[ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
FASTSMSEVO VERSION 0.1 AVAILABLE IN TESTING FASTSMS VERSION 0.5.8 AVAILABLE IN TESTING If you enjoy it: Donate Link to PayPal This plugin allows the use of FastSMS as virtual keyboard in all N900. Please report all of your problem here so I can try to solve. How use it?
What you need to know:
Well-knowed problem:
Next improvements:
Bug-tracker: https://garage.maemo.org/tracker/?at...60&func=browse |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Buuuuuump!!!
Kind Regards, D4rKlar |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
thanx a lot for this but isnt it possible somehow to run this virtual keyboard without fastsms app....maybe in the future?
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Woo been waiting for this for months! Ill donate.
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Cant find it in devel?
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Yes in devel (when maemo extra assistant move it).
Without FastSMS? why this? FastSMS in only a keyboard now... |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Let me suggest you to use a more generic name such as "Virtual Keyboard Replacement" or something like that. This way it will be more discoverable for noob users once it reaches Extras.
As said, it would be better if FastSMS depend on the Virtual Keyboard for the future. Good work, |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Got it, had to install via terminal
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
Sorry, but what do you mean with "As said, it would be better if FastSMS depend on the Virtual Keyboard for the future."? |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
installed via app manager..
i cant understand how cani insert text inside an sms.. btw it looks good, finally :) thanks!! |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Well done!
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
Start it from icon show "old" interface and allows to change options (language for example) EDIT: Added this answer to first post |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
but how can i answer to an sms? i have to put everytime the number..when i want to answer to a friend, it could be nice if number is just there written.. (an improvement for the future) :) |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
Virtual keyboard will be opened without recipient fields (if all works fine) and you only need to insert the answer and then tap out of keyboard. Your message will be displayed in text-field like you inserted via hardware keyboard So you DON'T have to use the icon in main menu... |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Question: Is FastSMS marked as a dependency of FastSMSEvo? I just glanced at the dependencies list for FastSMSEvo and didn't notice it, but I may very well be wrong about that, and just didn't see it.
@Minhaz: He'd have to recode both FastSMS and FastSMSEvo probably, to make that work. What I would have done is made FastSMSEvo stand-alone and then made FastSMS depend on and use FastSMSEvo. But I can understand why he went his route, since FastSMS was here first, so that was the natural progression coding-wise. Some quick test results: There is a slightly noticeable memory use difference. I use both the normal CPUMEM applet and my own python clone of it with five bars - cpumem applet shows bars at 30, 50, 70, and 90 % RAM used. Mine shows bars at 20, 40, 60, 80, and 100. Normally a new reboot puts both versions at two bars, implying memory use between 50-60 %. After launching FastSMS and letting it sit in the background [EDIT: Meaning, after I launched the VKB normally, and it loaded FastSMS in the background as is explained in the first post), my applet shows 3 bars, cpumem still shows 2 - implying 60-70 % memory used. Not an issue, and it could be the difference of 1-2 %, but just letting you know it's somewhat noticeable. I also JUST realized that the red/white icon button was an eraser, and that was backspace. For a while I thought there was no backspace at all. That icon is prob'ly a gamble in terms of intuitiveness, but it works, and so long as you know what it is it's not a problem to use. One thing I noticed (so far testing in Conversations only) is that if I auto-rotate conversations itself, it has a hard time rotating to portrait sometimes. The first time I auto-rotated Conversations and clicked on the text-box in portrait mode, the entire Conversations app flipped back to landscape, the FastSMS keyboard came up in landscape, then the entire thing auto-rotated to portrait then back to landscape... Or something like that. I then wiggled it a bit (landscape then portrait so that the system knew to flip again) and it went to portrait just fine. Testing it again for repeatability, however, I noticed that it launches in portrait mode from portrait mode Conversations just fine. It does, when you click out of the portrait VKB to enter text, go momentarily to landscape, exits the keyboard, and then Conversations rotates back to portrait. The text is entered just fine however. I had one instance of text NOT being entered when clicking out of the VKB when in landscape, I haven't really been able to reproduce it since though. I'll report back when I can with reports on how well it works in a bunch of other apps, but in the meantime I just want to say: this is wonderful. Suddenly the N900s versatility just skyrocketed tremendously on top of all the other great things about it. |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
@Menatlist: As always thank you for your feedback :)
Start from memory usage: FastSMS uses 6-7% of memory itself, but you have to consider that qtLibraries must be loaded so the total amount is 12-14% (depends on which language are you using). Consider that QtLibs are shared between different apps so they exists only once in memory (tools like Conky give the amount of memory with libs included). There are some part of old implementation that could be removed freeing memory, but I have to manage people that perhaps want use fastsms standalone and not as vkb. Icon: if someone wants draw a set of icon I will be happy to change all...They comes from different author and perhaps could be not so intuitive. Some problems about autorotation happens when device is parallel to ground (for example over a table) this is because orientation is "unknown". About non-commited text I've only experinced this in microB (like I said in first post) never in other place. Where you get this? |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
I figured out what makes it fail to enter text in Conversations (possibly applies elsewhere): If you already have text IN the text entry field BEFORE you open this vkb. When you launch it, it'll properly keep the text that's already there, but it'll fail to add the next text. (Doesn't matter if the already there text was entered with hardware keyboard, or by the same virtual one just a few seconds earlier.)
Just did preliminary X-Terminal test - vkb doesn't seem to want to enter text there. I actually DID get it to enter text in X-Term once, I just don't know how I did it/why it worked that one time. To clarify: If I have "Test" typed in the Conversations - say, I use the stock conversations program to send a text message - and type "Test" (with virtual or hardware keyboard, doesn't matter which). Then I close the Virtual/Hardware Keyboard, and click on the text box there "Test" is already entered, to bring up the vkb again. Then I type "blah" so the whole text looks like "Testblah". When I exit the VKB this time, only "Test" remains. - Edit - The icons are fine, but I'll be happy to draw you a generic backspace arrow if you'd like. As for taking care of the people who want to use FastSMS stand-alone, I agree. I'm just wondering if perhaps FastSMSEvo can be a dependency for stand-alone FastSMS (and then some of the necessary code would get moved to FastSMSEvo from FastSMS), and then people who install FastSMS (and thus FastSMSEvo) could have an option in the settings to use the FastSMS keyboard just system-wide or just for FastSMS (or these settings can be available in a Settings menu applet...). Either way though, I realize it's extra difficulty to do that. I think the way you have it right now is just fine. Also, re: orientation - I know. I assure you I was keeping it very definitively portrait/landscape. None of the wierd flipping happened during flat 'unknown' orientations. (But like I said, the really weird flipping was a one-time thing near as I can tell, and the click-out-of-keyboard->everything-goes-landscape-until-keyboard-closes->goes-back-to-portrait thing is minor and isn't a problem.) |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
uhm...strnge behaviour...did you reboot after install? I'm doing this test in conversation: put a letter, close,reopen, put a letter close...
I've write "hello how are you" in this way without problem...and in X-Term all works fine...Only consider that also standard kb doesn't reopen with entered text in x-term EDIT: Did exactly your test and all works fine BUT I've noticed this problem in microB during my tests so the problem exists and not only in microB. If I can find a way to reproduce this bug always I can fix easily |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Hmm, am I supposed to get the whole FastSMS interface loaded when the keyboard should show?
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
(Just added more reply in my last post as an edit.)
Anyway, strange indeed. I did reboot. I turned on FastSMS once by itself to check the settings right after reboot, if that helps? I have a few python status menu applets running in the background.. Nothing that SHOULD change our results, but I may well have something wrong going on on my device. I say we wait and see what other reports come in. Mine might be the odd-N900-out. |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
is Possible switch from original keyboard to it ?
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Do you have a git repository somewhere?
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
Thanks for your work, though. :) |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
|
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Weird, all of FastSMS is being started at each click of an input box.
And yes, I tried rebooting. |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
If yes try this: Code:
dbus-send --print-reply --dest=it.rsc.fastsms / it.rsc.fastsms.surroundRequest string:"test" |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Hmm, so I need fastsms 0.5 and it doesn't depend on it?
Add Code:
Depends: fastsms (>= 0.5-0) |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Hey - I just noticed - it randomly started mostly-working for me on the inputting text front.
I still occasionally don't get it to work, but mostly it does. Nearly as I can tell, it has something to do with pressing ON the text, instead of in the empty space, in an input box when text is already there. Which, of course, probably doesn't make any sense at all from a code stand point why that should be. (XTerm use is still the buggy for me - the already entered text doesn't show up in the vkb - though it does add new text on somewhat consistently if I open/close/reopen the vkb.) - Edit - Okay, X-Term just works if I click on the line where text is being entered, If I click on the text or off the text is cool, but it has to be on that one line. Which I could've sworn I was doing before, but whatever. Working nicely now. I'll just shut up now until I can do more testing/fiddling. |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
Feel free to message me if I don't notice it for some reason (I'm fairly busy). |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Quote:
@Mentalist: X-Term doesn't works well neither with standard vkb: already entered text is not displayed when opening vkb and text added will be appended. I noticed tha same things you said about pressing on text/free space but only one time, the first time...so I'm starting to think that this is a problem with d-bus... EDIT: I've added dependecy to fastsmsevo and some log print. Also fastsms have now a print before sending the text. Please download it (when available, fastsmsevo-0.1-6 fastsms-0.5-1) so we can understand a bit more |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
I guess the bug Metalist reported is due to this
Code:
#if defined(Q_WS_MAEMO_5) |
Re: [ANNOUNCE] FastSMSEvo: system virtual keyboard T9/Qwerty
Hey i have a question
How do you go to a new line (enter key) in the alpha numeric keyboard? Best Regards Unit247 |
All times are GMT. The time now is 15:01. |
vBulletin® Version 3.8.8