Notices

Originally Posted by Taomyn

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.

Originally Posted by Laughing Man

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

Originally Posted by euanandrews

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.

Originally Posted by anapospastos

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).

Originally Posted by dwould

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>

Originally Posted by jgbreezer

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)?

Originally Posted by jgbreezer

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!

Originally Posted by jgbreezer

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

Originally Posted by skr0

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 ?