Once you've collected the inputted text string, how do you actually send the sms message? What I mean is, which api do you use for that? I thought that was part of Qt Mobility which isnt available yet, is there another way to access the basic phone functions?
Edit: never mind, found it

To answer a question above, the sms conversations are stored on a SQLite3 database (“/home/user/.rtcom-eventlogger/el.db” if i remember right) so it should be possible to read and write messages from other apps to there.

Considering how I got the letters to display in the first place, anything that improves the appearance even slightly that doesn't hender performance is welcome in my book. I'm applying this to my branch until ossi has a chance to look at it in the meantime.

As for table, perhaps that would be the better way to go considering it would make things a bit more uniform. I swore off gtk some years back* so this is technically the only gtk app I've ever contributed to. Perhaps ossi can have a look at that. Alternatively, patches are welcome ;-)

* I find Qt far more intuitive and the rediculously long names in (py)gtk irk me.

[edit]
I'll probably sanitize the variable names before I request for a merge though, qwerty12. ****ing hilarious though.

Stay away from those for loops, then.... The rest should be fine, though.
I wish there was a better way to get to the GtkLabels but the fact that HildonButton doesn't have any methods for retrieving its Labels and that the buttons are not in an array, means I have to use a million for loops to iterate through all the widgets and their children and use eval...

Looks like we're total opposites, then I <3 GTK+ (though I won't pretend to be competent with it) and using it with Vala makes me feel all giddy

Lol. At any rate, looks like implementing a table instead of boxes will not only be trivial, but will help clean up the code -- and help you help us style the widgets :P

Off topic- you seem to be all over the place when code is discussed qwerty12 -- no wonder your thanks rival your posts. BTW, thanks for cleaning up the print statements, I forgot you could concat strings like that.

[edit]
I've replaced hboxes with tables, but the line that changes button_send's name breaks the button. Without it, the styling is gone, but everything looks normal. I'm going to play a bit with the sizing attributes and see if I can come to a compromise.

[edit 2]
Seems the issue is related to this post, although no one has responded :-(

Similar to the above post, trying to use thumb height causes errors. The only work around as of yet is to go back to hboxes :-S

Ok, I sorted through the issues, and now all buttons are properly themed and uniformly shaped:

damn its lookin good already! someone package it so we can test!

it should work if you have python in your device installed. just download vertsms.py from:
http://www.gitorious.org/vertsms

and at command line

that is in todo-list. it only sends the sms and no trace is left nowhere unless you are logging dbus activities...

Here is just simple mockup

- Padding between buttons
- arrows to move, send button to different place so you do not accidentally push it when texting (was too close to 8, 7, 0)


portrait SMS screens from other touch phones:
http://www.tecfre.com/uploads/2008/1...0_tube_sms.jpg
http://www.slashgear.com/wp-content/...w-part-1-1.jpg
http://www.infonokia.pl/agrocms/tmp_...ssmusic-29.jpg
http://blog.smub.it/wp-content/uploa...iphone-sms.jpg

great work !!! keep it on this app is a dream for n900 users