maemo.org - Talk - witter - a python twitter client

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - witter - a python twitter client (https://talk.maemo.org/showthread.php?t=35596)

Re: witter - a python twitter client

I'm having trouble myself..

Code:

$ run-standalone.sh python2.5 /opt/witter/witter.py

no service setting

No more users to load

Establishing api for Twitter using basic auth

Connection working ok

Failed to load cached timeline

Failed to load cached timeline

Traceback (most recent call last):

  File "/opt/witter/witter.py", line 1148, in <module>

    app = Witter()

  File "/opt/witter/witter.py", line 171, in __init__

    self.activeAccount.dmstore = self.reload_timeline_data('/home/user/.witterdm',self.activeAccount.getDmsList())

  File "/opt/witter/witter.py", line 644, in reload_timeline_data

    tweetstore.append([senderName,senderId,tweet,"",tweet_long_id,type,createdAt,replyTo,source,avatar,formattedTweet])

UnboundLocalError: local variable 'avatar' referenced before assignment

Re: witter - a python twitter client

Quote:

Originally Posted by Taomyn (Post 699306)

Liking what's been happening to Witter the past few months, I tended to stay away from it as I felt it a little difficult to use. A combination of your hard work and PR1.2 seems to be helping a great deal.

If I had one wish, that would be for the text input area to only appear when I want it - having to hit refresh, thus wasting API calls, is a pain and I really don't see why it should be there by default seeing as it's simple enough to get it to reappear once it's gone.

Keep up the great work.

P.S. Please update the first post of this thread - your blog post is, to be exact the comments section, very difficult to read at times with it's almost random layout - it's not obvious where the latest messages are.

the main issue with hiding the text box is having an event to hook it's dissapearance from. either an extra button, or some kind of timer thread. i'll give it some thought, but it's not as simple as it sounds.

as for the blog, i'll look into it. the comments threading is a little difficult.to follow.

Re: witter - a python twitter client

Quote:

Originally Posted by Laughing Man (Post 699470)

I'm having trouble myself..

Code:

$ run-standalone.sh python2.5 /opt/witter/witter.py

no service setting

No more users to load

Establishing api for Twitter using basic auth

Connection working ok

Failed to load cached timeline

Failed to load cached timeline

Traceback (most recent call last):

  File "/opt/witter/witter.py", line 1148, in <module>

    app = Witter()

  File "/opt/witter/witter.py", line 171, in __init__

    self.activeAccount.dmstore = self.reload_timeline_data('/home/user/.witterdm',self.activeAccount.getDmsList())

  File "/opt/witter/witter.py", line 644, in reload_timeline_data

    tweetstore.append([senderName,senderId,tweet,"",tweet_long_id,type,createdAt,replyTo,source,avatar,formattedTweet])

UnboundLocalError: local variable 'avatar' referenced before assignment

what version. I'' pretty sure i fixed that in -10. but I may have messed up and not promoted that version to testing. I will fix the current missing dependancy, and push that verison up to testing to get both issues resolved

Re: witter - a python twitter client

Quote:

Originally Posted by euanandrews (Post 698898)

I am using the latest version with the portrait on-screen qwerty....very nice work Daniel....

Is it possible you can make the qwerty function whenever a user types/presses in the tweet/text box....rather than having to press the + to make it appear?
Exactly as done when in landscape mode.

that was the plan, but i didn't find the relevent signal to connect to when I looked quickly, and i wanted to get it out in some form quickly.

obviously in that model i'd also need to use a key on the keyboard to dismiss it again.

may find time this weekend to investigate varius signals that i can use for this kind of thing

Re: witter - a python twitter client

I 've seen much improvement in witter. Kudos to dwould. Greek language in portrait keyboard would be a nice addition:) And if its possible to count every character as 1 and not 2(in greek language too).

Re: witter - a python twitter client

Quote:

Originally Posted by anapospastos (Post 700952)

Yeah, internationalisation generally is something I've considered, the main problem (and it;s a selfish one) is that it's a lot of work for something that I don't need, and can't even test properly.
basically I'd have to shift from the easy just using hard coded strings where I need to, to having to have message files and load references to everything. And then I could get volunteers to creates translations of those message files.
I'll think about it, if I can dream up a fast and simple way to convert what I've done so far.... then maybe.

Re: witter - a python twitter client

Quote:

Originally Posted by dwould (Post 699897)

the main issue with hiding the text box is having an event to hook it's dissapearance from. either an extra button, or some kind of timer thread.<snip>

dwould, ta for the strides forwards with this app in the last few weeks. With portrait support and fixed bugs its starting to be quite usable.

Indeed, a timer would be the best way to make the textbox disappear when not in use and the accepted way for other things (am thinking particularly of javascript timers, though that might be lots easier to setup than python+system libraries). Is there an easy interrupt handler kinda thing equivalent (am a c++/linux/python dev but not used to event-driven models yet in native app UIs)?

Obviously getting the text box back again is easy in one way (any keypress event on the main screen opens it up with the key you pressed pre-inserted), but when you're using the virtual keyboard it might be harder (I mean is there another way, apart from clicking a "reply" button from another opened post's window). You could overlay a small button bottom-left (you might not care that you'd cover up an avatar from the bottom post on the screen) that only appears when the hardware keyboard is shut, or steal one of the other hardware buttons (camera button? Probably lots of effort but there might be other apps that provide libs/ways to do it).

I used to get just a busy-wait indicator when I went to "mentions" tab (even before PR1.2), and it never got the tweets/updated; now it shows stuff, and it doesn't lose it when you switch tabs back to it either now. The other windows still seem to be empty though, or take forever. But keep going, its getting better and better!

If I felt I had a good amount of time to spare I'd offer you some coding help (I've slowly been getting to know the pygtk libs the last couple of months by writing my own basic tube station/line info app) and have a little experience with internationalisation from previous paid contracts in python/php.

PS... from your blog, v3.3.7(I think?), I quote:
"Initial support for starting a connection if none exists, currently it starts, but not before witter fails the connection is was trying. not sure yet how to make witter wait for active connection"

Did you fix this? I'm wondering if there's a dbus message you can subscribe to to know when its connected, either that or just retry the socket open for a period of time (or set the socket timeout larger?). There's gotta be a standard way to do it like the builtin Nokia-selected/built apps do.

John, London, UK

Re: witter - a python twitter client

Quote:

Originally Posted by jgbreezer (Post 701075)

I'm pretty sure for dissapearing under inactivity I could just spin off a thread which counts down, and everytime a key event occurs it's counter gets set back to initial value.
I really just need to have the time to figure out if there is a focus event that I can connect to for when someone taps inside the hildon Entry field..

Quote:

Originally Posted by jgbreezer (Post 701075)

Obviously getting the text box back again is easy in one way (any keypress event on the main screen opens it up with the key you pressed pre-inserted), but when you're using the virtual keyboard it might be harder (I mean is there another way, apart from clicking a "reply" button from another opened post's window)

I used to get just a busy-wait indicator when I went to "mentions" tab (even before PR1.2), and it never got the tweets/updated; now it shows stuff, and it doesn't lose it when you switch tabs back to it either now. The other windows still seem to be empty though, or take forever. But keep going, its getting better and better!

Not entirely sure what you mean? timeline/mentions/dm should load at start up, but then only refresh if you have set auto refresh intervals in preferences. Everything else stays blank until you explicitly request a refresh. (search obviously needs search terms, userhistory needs a user name to search for)
Are you saying that even when you ask for a refresh some of the views don't load?

Quote:

Originally Posted by jgbreezer (Post 701075)

If I felt I had a good amount of time to spare I'd offer you some coding help (I've slowly been getting to know the pygtk libs the last couple of months by writing my own basic tube station/line info app) and have a little experience with internationalisation from previous paid contracts in python/php.

PS... from your blog, v3.3.7(I think?), I quote:
"Initial support for starting a connection if none exists, currently it starts, but not before witter fails the connection is was trying. not sure yet how to make witter wait for active connection"

Did you fix this? I'm wondering if there's a dbus message you can subscribe to to know when its connected, either that or just retry the socket open for a period of time (or set the socket timeout larger?). There's gotta be a standard way to do it like the builtin Nokia-selected/built apps do.

John, London, UK

nope not fixed the connection thing yet. I'm using conic, and I *thought* I'd set it up such that I should get a callback for connection events, but it's not firing, and I've not had time to figure out why yet.

Re: witter - a python twitter client

I seem to get a lot of 'server returned 400' type errors using Oauth so I competley uninstalled witter including deleting .witter* files fom mhy Home directory.
Installed v 0.3.4-2 without using Oauth I do not get any tweets, just the 'server returned 400' error.

Do you recommend using Oauth or not ?

Re: witter - a python twitter client

Quote:

Originally Posted by skr0 (Post 701423)

use Oauth, twitter are due to completely remove support for basic auth this month.
400 errors are often associated with hitting your API rate limit.
Go to this URL in a browser: http://twitter.com/account/rate_limit_status.xml
and see if you've hit your limit which is something like 150 requests per hour.
So for instance if you have timeline/mentions and DMs set at 1 min check interval, then you'd reliably blow that 150 limit every hour, and have to wait for the end of the hour to reset.