Notices

Originally Posted by fcrochik

I am working on a "phonebook/contacts" application and would be quite easy to create an interface to launch your application with a phone number for a contact.

check it at: http://talk.maemo.org/showthread.php?t=55513

Ideally we could just create a Dbus message for that. Is your application written in C++/QT?

Originally Posted by realsportcars

@maxximuscool: buttons takes colour from selected N900 theme.

@woody14619 and eitama: Did you use english-full dictionary? If yes try to switch to english normal and let me know. english-full is very big and not really good for use atm.

@woody14619
1> It takes forever to "digest" the dictionary on the first run. Maybe you want to pre-digest the given dictionaries shipped?

Maybe Yes: the reason for leave this works on first start is because other users can easily add their language. In a second moment, when i can include more commons languages i will give pre-compiled dictionaries

4> It guesses words alphabetically from what I can see, and doesn't remember or weight the word usage in any way. If I type in a longer word it usually gets it right after 4 or 5 letters, but smaller words that start with the 3rd or 4th letter on a key are never the default word, despite their more prevalent usage.

I'm not sure to understand what you mean but i will try to answer: at the start words are proposed in alphabetical order, but if you try to write "How are you" the next time you will have "how" "are" "you" as first choice.

@eitama
2. Switching to portrait mode doesn't always work (with auto-rotation)
Yes, i know. but unfortunately i cant find a solution and i did some tries
3. I press the letters, and nothing happen, They don't fill the textbox (entry)
Do you mean that the main function doesn't works? If yes try to open the option,switch to another language and then reselect yours

Originally Posted by eitama

Hey!

1. Yes I was using the full English one, switched to lite and indeed everything works much better now.
2. The application is unusable in it's current condition imho, i'll explain :
- I'd like it to take me less time to send an sms using FastSMS then with the native Conversations interface that came with the N900, but the word selection of the dictionary is slowing me down.
An attempt to type : "Hey mate, what's up?" took me really long cause I had to rifle through the matches to find the words I wanted.
The most used and common words need to get priority over the rest - I know it's lots of dirty work, but you could try and gather statistics from the users, and upload them to some server, and then allow distributing those statistics with updates.
3. I am missing a newline key. (:

Cheers!
Eitam.

Originally Posted by cjard

this is a really good opportunity to fix what has been broken with nokia T9 style texting on other phones for years.. my suggestions here will bring the best aspects from symbian T9 and sony ericsson texting (sony's system is better than symbian in many ways)
This feedback contains reference to <NEXT> and <PREV> as the key that moves to the next guess and the previous guess respectively

[...]


Gotta say tho, I've found very few bugs in the app and i'm impressed how well it handles things generally. It's looking good, and could realise all my dreams of things i've complained about with regard to symbian texting for years.. If you want any assstance with it, from a data file, gui or qt point of view (my qt isnt amazing, but I'm getting there with it - i'm a c# guy normally) then just ask - it would only be fair of me to offerto help implement my long wishlist here

Originally Posted by realsportcars

1-Good, however i will arrange memory usage in next release.
2-Your idea on statistics is really hard to implement: how send statistics? where? and overall: users maybe are not happy to know that someone know what they are writing!!! FastSMS is designed to learns more used words. After 10-20 perhaps 50 sms more commons words are on the top of the list
If you write "Hey mate, what's up?" in a second message all of these words are the first choice! However i think that the actual system is not the best: i have to think about it to understand how i can change it
I know that first run are not so comfortable but atm there are no others solution. If someone will use intensively the app and wants to send the dictionary file i will happy to analyze it and reorder words
3-Yes, you are right i will add asap

Originally Posted by eitama

Thank you for taking my requests into consideration!
I understand what you mean about the privacy issues, indeed they exist - but you could put this as an option (default off) to report anonymously & manually, even more, keep a list on the phone of words that have been used with a counter per word,
then you go into the option, choose "Report usage" and a list with the words and checkboxes will appear, you can unselect the ones you don't like.

The reporting part is pretty easy, and HTTP post containing an XML body with a simple syntax like :

Code:

<root>
<word>
<name>hello</name>
<count>5</count>
</word>
<word>
<name>roommate</name>
<count>5</count>
</word>
<word>
<name>car</name>
<count>7</count>
</word>
</root>

On the server side, you put PHP or ASP or Perl or C# and parse this, and automatically insert it into a dictionary.
I can help on the server side if you need - the only thing you need is a dedicated server (:

Another option :
You could also run a scan on the conversation history on 10 phones, and use that as a base statistics.

Originally Posted by cjard

this is a really good opportunity to fix what has been broken with nokia T9 style texting on other phones for years.. my suggestions here will bring the best aspects from symbian T9 and sony ericsson texting (sony's system is better than symbian in many ways)
This feedback contains reference to <NEXT> and <PREV> as the key that moves to the next guess and the previous guess respectively

here's the feedback:

Landascape spelling should be "Landscape"

If I enter a sequence of periods ........ then delete them all and enter just one period again . then the <NEXT> key doesnt change the guess.. It's stuck as a period?

The dictionaries seem to contain some junk - i try to write the english word BE and i get CF CE CD - none of these are english words. If you'd like me to prune the dictionary files for you, just pass them along

It also doesnt seem to suggest in alphabetical order (i think i remember reading that it did) words that havent been used yet?

Program should suggest words with accented characters with lower priority than non accented.. e.g. i'm using english lite dict and I want to write "he", i press 43 and I get IE ID HÉ HF.. eventually HE comes around, but I wonder why the word order is that the accented char is first. Perhaps we should grab some long texts in english (like War and Peace or the bible) and break them into words, counting each word, and provide fastsms dictionary files with words already arranged in the order of most popular to least popular?

the word priority might frustrate the user:
if I write HE, the next time, it will write HE. If I write HE ten times, then write IF once, the next time it will suggest IF first.. i.e. it seems to work in a "most recently used" mode, not a "most often used" mode
Most often used mode is better - if you have MRU mode, users will get confused because the suggestions will always be jumping around.. Suppose they write HE ten times to every one time of IF, the user gets a "memory" in his fingers that HE is 43, and IF is 43<NEXT> but if youre always switching around the word order based on MRU, this logic doesnt hold and it will slow down the texting and frustrate the user

Originally Posted by aspidites

Why do you have to restart just to set the orientation? I implement the same kind of setting and it takes affect immediately. If you haven't already, take a look at QSettings. I just called a method after I changed the orientation setting which set the appropriate attribute accordingly.