Dialcentral 1.0 - Page 117 - maemo.org

epage | # 1161 | 2010-03-01, 16:18 | Report

Originally Posted by mrdally204 View Post

You keep asking me to file the request, but I hate searching through the posts to remember where to post them. Can you add the link to your Signature to save us all some time please

Also in my signature is a link to the website for DC. On the downloads page there is a link to view all the DC bug reports and enhancement requests as well as the link to file them.

The Following 2 Users Say Thank You to epage For This Useful Post:
Addison, iKneaDough

iXce | # 1162 | 2010-03-05, 03:59 | Report

Hm, if you use DialCentral with a locale which does not use PM/AM time format, you can't get the calls history or messages list, but you get instead a "unparsed data remains: AM" error (or something along the line). This is due to the fact that the %p in strptime is user locale dependant : the parsed uses C (or so), while strptime doesn't expect any thing behind %p since my locale (fr_FR) uses 24 hours time format.
I've written a small patch against latest git that temporarily switches the locale to C when parsing such dates. It's not /that/ clean but it works, and I don't see a cleaner way of doing this.

Thanks for this awesome piece of software anyway

PS : i don't know if this affects TOR, I haven't been able to try yet

Attached Files

0001-Fix-time-parsing-when-the-user-locale-does-not-use-A.patch.txt (2.7 KB, 90 views)

The Following 3 Users Say Thank You to iXce For This Useful Post:
Addison, epage, mrdally204

iXce | # 1163 | 2010-03-05, 22:33 | Report

Actually, this first patch worked great on my computer but not on the n900. A simpler (which avoids tricking strptime and all) patch is simply to handle the ValueError exceptions which are /probably/ caused by the extra AM/PM and to do the AM/PM conversion by hand. If the ValueError was not caused by this, it should occur again on the strptime-without-%p call anyway. I attached the corresponding patch. Works great on both my computer and n900 !

Attached Files

0001-Fix-time-parsing-on-locales-which-do-not-use-AM-PM-f.patch.txt (2.5 KB, 87 views)

The Following 3 Users Say Thank You to iXce For This Useful Post:
Addison, epage, mrdally204

epage | # 1164 | 2010-03-06, 00:08 | Report

Originally Posted by iXce View Post

Actually, this first patch worked great on my computer but not on the n900. A simpler (which avoids tricking strptime and all) patch is simply to handle the ValueError exceptions which are /probably/ caused by the extra AM/PM and to do the AM/PM conversion by hand. If the ValueError was not caused by this, it should occur again on the strptime-without-%p call anyway. I attached the corresponding patch. Works great on both my computer and n900 !

I've applied it and sent it to the autobuilder

EDIT: Once its been built, could you run it out of extras-devel and check that it all worked out before I promote to extras-testing?

Thanks

Last edited by epage; 2010-03-06 at 00:10.

The Following User Says Thank You to epage For This Useful Post:
Addison

iXce | # 1165 | 2010-03-06, 21:34 | Report

Updated to 1.1.8. Message list and call history works like a charm ! Thanks !

The Following User Says Thank You to iXce For This Useful Post:
Addison

Addison | # 1166 | 2010-03-10, 06:23 | Report

Hey Ed!

So I've been thinking a little more about having a fuller, touch screen keyboard to be used with DC.

The only trouble that I'm seeing is that you're showing the message history when sending a reply text.

Because of this, the area that you're typing in isn't at the top part of the screen.

I know you really like the way it presents on the screen since you have a hardware keyboard, but is there any possible chance of getting a compromise out of you?

Here's a quick and dirty first attempt at the new keyboard layout.

mrdally204 | # 1167 | 2010-03-10, 06:57 | Report

I would prefer a keybaord face similar fto better keyboard. http://betterandroid.wordpress.com/2...d-for-android/
This would also allow for "portrait mode" to be an option if you can have the OSK built in when in portrait mode.

Is there a way to build a "skin-able" keyboard into an app?
It would be fun to be able to make and change out you keyboard as you see fit.

This would also be an excellent project if any coders are bored. Make a Open source skin-able keyboard that can be easily ported into other applications to use.

Last edited by mrdally204; 2010-03-10 at 07:00.

The Following User Says Thank You to mrdally204 For This Useful Post:
Addison

Addison | # 1168 | 2010-03-10, 07:14 | Report

Yep, I already mentioned that I'll probably end up with 10 keys per row. That seems to make the most sense now that I think about it.

While xkbd isn't exactly skinnable, it does allow the option of using a graphic image of each key instead of just plain text. So having a sexy keyboard is definitely possible, it just will take more time than expected.

If you want to help out or share more of your ideas, join in on our current discussion, mrdally.
http://talk.maemo.org/showthread.php?t=39919

Addison | # 1169 | 2010-03-11, 02:27 | Report

Oh hey, I forgot to mention one other request.

In DC, when you're checking to see if there are any new additions to the message history, if so, then you trigger the LED event....

Would it be possible to insert a line of code to check if the beginning of the message starts with "Me:"? If it does then don't set off the notification event.

It wouldn't work with sending the first SMS, but after that, it could reduce having to constantly refresh the conversation by 50%.

Is this an idea you like?

If so, I could file a request for it.

Cheers.

The Following User Says Thank You to Addison For This Useful Post:
mrdally204

x61 | # 1170 | 2010-03-11, 02:41 | Report

Is it possible to add contact in Dialcentral? I cant seem to be able to do it.