Since the last update I feel that witter is a fully useable twitter client for me, and the only one I use while on the move. A couple of minor things bother me though, all of which should be pretty trivial to fix:
A link like this : "mece66: iron sky (http://www.ironsky.net)"
is parsed, but the ( ) are included in the url, so the browser wont open it properly unless you manually remove the parantheses..
some special characters, for example < and > are html encoded and are displayed like
Code:
<
so they need to be decoded when displayed, for example with HTMLparser.unescape IIRC.
the RT function is rendered wrong imo. it's now "RT: @mece66 : blahblah" and it should be "RT @mece66: blahblah"
RT function should work on too long texts, but cut off the end if tweeted while too long. -14 chars left or something like that could be displayed if text is too long.
lastly, and this might not be a bug, just me... How do I use twitpic? I mean where do I enter the text? What happens when I click the "twitpic" button after selecting an image?
Since the last update I feel that witter is a fully useable twitter client for me, and the only one I use while on the move. A couple of minor things bother me though, all of which should be pretty trivial to fix:
A link like this : "mece66: iron sky (http://www.ironsky.net)"
is parsed, but the ( ) are included in the url, so the browser wont open it properly unless you manually remove the parantheses..
i wouldn't expect a url like that to be parsed, snce i look for 'words' that start http however if urls end with random chars then how do i know what is url and what is not? at the moment i assume a url starts with http and ends with a space.
not sure how else to do this.
some special characters, for example < and > are html encoded and are displayed like
Code:
<
so they need to be decoded when displayed, for example with HTMLparser.unescape IIRC.
the text is rendered using pango, which is like html, it would interpret unescaped < chars as relevant to it's markup. not sure how to make it render those normally.
RT function should work on too long texts, but cut off the end if tweeted while too long. -14 chars left or something like that could be displayed if text is too long.
doesn't it do exactly that now? eg it puts whole tweet in place but with -14 indicator?
lastly, and this might not be a bug, just me... How do I use twitpic? I mean where do I enter the text? What happens when I click the "twitpic" button after selecting an image?
br, @mece66
write you comment in entry field, then go to twitpic menu option select picture. when you hit 'twitpic' picture and comment are sent.
currently if there is no text in the entry field, it doesn't send.
I'm aware this needs a proper pop up warning, or just to post with no comment
i wouldn't expect a url like that to be parsed, snce i look for 'words' that start http however if urls end with random chars then how do i know what is url and what is not? at the moment i assume a url starts with http and ends with a space.
not sure how else to do this.
ok fine, it did however parse it for some reason. there was a button with open url (http://asdf) and it opened that exact string in the browser. Weird stuff.
the text is rendered using pango, which is like html, it would interpret unescaped < chars as relevant to it's markup. not sure how to make it render those normally.
That one should render properly if markup is used, so the problem is somewhere else. For example double escaping the & character would do this, making the string &lt; instead of <
Perhaps line 799 in account.py version 0.3.1-9?
so the problem is the : after the RT? or also the space after username? again I detect usernames as starting with @ and ending in a space.
Well both of them, as they are redundant characters. Perhaps one could parse users starting with @ and ending with space or :
anyway I now just manually edit the thing, but the "RT @user:" method seems to be commonly used. (tweetdeck, echofon and gravity use that method at least)
write you comment in entry field, then go to twitpic menu option select picture. when you hit 'twitpic' picture and comment are sent.
currently if there is no text in the entry field, it doesn't send.
I'm aware this needs a proper pop up warning, or just to post with no comment
0.3.1-10 includes support for themed icons.
anyone can create a set of icons with the same filenames as the default theme and make them availiable to witter.
basically just create a folder under /opt/witter/icons/
that is the name of your theme, and in that folder place you icons (default icons are all 48x48)
then run witter and your theme will show up in preferences->select theme
themes could be made separately installable just need to put their files in the right place.
see my blog for full list of icon files required.
