Re: witter - a python twitter client
 

Does this application supports network proxy? (like will it respect the systemwide proxy settings or does it has it’s own embedded proxy settings? Thanks for doing this and keep up the good work

Re: witter - a python twitter client
 

ok, so it took quite a bit of reading and learning. and now the 0.1.1-6 is on it's way through the auto-builder.

At long last witter has auto-refresh.

Main timeline, mentions, dm's and public timeline all support auto-refresh, and can be independently set to different intervals.

This update also includes some layout changes, the addition of character counter. some other minor fixes.

There are some problems I've not figured out yet. specifically if you cancel a dialog by clicking outside it, rather than the cancel button, then when you try to come back to the dialog again, it doesn't come up properly. This effects the credentials and the new properties dialogs.
If anyone knows why this happens..I'd love to hear from you.

updates images of the new version can be found at my blog: http://danielwould.wordpress.com/witter/

At the rate the auto-builder is going, it may be tomorrow morning before 0.1.1-6 is actually availiable in extras-devel

Re: witter - a python twitter client
 

I just installed witter yesterday.

Is anyone having the same problem like mine? I can't seem to use the twitpic function. Every time I tap on it, the app crashed and I need to restart it again. I tried putting comment 1st, then twitpic but same thing happened.

Re: witter - a python twitter client
 

n900 or n8*0?
could you try running witter from the commandline and see what it outputs?
and do you mean when you tap on the menu optin, or when you have selected a picture and tap the twitpic button?

Re: witter - a python twitter client
 

FYI, witter 0.1.1-7 finally available in extras-devel for n900.

I'll be interested to see if the auto-refresh works ok for people that wanted it.

Re: witter - a python twitter client
 

Wonder what's wrong - first I couldn't update it, decided to uninstall and re-install. Only that now I can't even find it in the repository anymore :/

EDIT! Found it finally and installed perfectly this time :)

Re: witter - a python twitter client
 

if you hit a point when it was still 0.1.1-6 in the repo, then that would have failed to install. otherwise I have no idea why.

Wondering wether to package up my saved searches additions, or to hold off to avoid overloading people with updates

Re: witter - a python twitter client
 

0.1.1-6 was the one. Made the N900 a bit confused. Update once a day is OK I think - at least in the early stages.

Re: witter - a python twitter client
 

This morning brings 0.1.1-9 to extras-devel, the most important feature of which is a new logo! courtesy of @mece66.

However it also bring support for multiple searches. In the search view you can enter multiple searches separated by commas in the text field. and a search will retrieve each.
Everytime you refresh it will remove the previous results, so it will only ever show the most recent 20 for each search term.

it will also save these searches, if you flip to another view and back the search items will be repopulated in the box when you come back to the search view. It also saves them between sessions.

To go with this, you can now specifiy a refresh interval for the search view, just like with other views. So you can set your favorite search terms, and select a refresh rate and it will keep updating them.

assuming no major problems found, I may promote this one up to extras-testing. As the next things I can think to work on are likely to take me a while.

Re: witter - a python twitter client
 

I believe 1.1.9 is not storing credentials (a filesystem permissions problem? BTW: Better store config things in GConf).

In fact, while the app shows up, I can't see any twitter content. All UI is there and I can do "Set UID/PWD". However, trying to send a Tweet then gives me an error "401, not authorised: check uid/pwd"
After quiting and restarting, UID/PWD still is empty.

(Starting from Terminal shows "store_creds called" after OKing "Set UID/PWD", so this step looks good. Where are the creds currently stored?)

The only thing that work for me is the [search] function (as this is probably anonymous). Still really cool to see all the Japanese and Arab results in their native fonts :-)