Remember the last update

[GoogleCodeExporter]

I'm currently trying Pino 0.1.0b2 from the PPA repository. After a first
try, I like it very much.

Here are a few  thoughts:

1) most important: remember the time of the last update. After starting
pino, the whole timeline is highlighted as unread. That's not good. ;-)

2) unread tweets appears darker than read tweets. I'm using shiki-dust as
theme, but it look much like the standard human theme on your left
screenshot. I think it should be the other way round. Or just add a unread
marker like a green point (like a LED). For example in front of the authors
name.

3) Like pidgin or tranmission, pino should not exit while pressing the X of
the main window. With an active tray icon, the main window shoul close but
the application should still be active.

At the end, thanks for such a lean and fast tool.

Original issue reported on code.google.com by joerg.desch on 13 Dec 2009 at 4:48

[GoogleCodeExporter]

Sorry, but the issue type is wrong. google-code did not ask for it...

Original comment by joerg.desch on 13 Dec 2009 at 4:49

[GoogleCodeExporter]

Sorry to add one more comment.

If you want to implement the storage of the last update, please store it inside 
a
separate file. I think one file per account would be great. Thi should make the 
sync
with other PCs easier (PC <-> Laptop).

Original comment by joerg.desch on 13 Dec 2009 at 5:24

[GoogleCodeExporter]

> After starting pino, the whole timeline is highlighted as unread.

This is very strange. Can you give me your time zone and system locale? 

Original comment by tro...@gmail.com on 13 Dec 2009 at 6:38

[GoogleCodeExporter]

> Can you give me your time zone and system locale? 

$ cat /etc/timezone 
Europe/Berlin

$ locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"

Is this enough? By the way... where do you store the time of the last update?

Original comment by joerg.desch on 14 Dec 2009 at 6:19

[GoogleCodeExporter]

Sorry, I can't reproduce your problem. I'll wait for confirmation from other 
users.

> Is this enough? By the way... where do you store the time of the last update?

Nowhere :) After starting Pino asks for a complete timeline. After that it 
requires 
only new tweets from last updating. If you asking about source code, this is 
attributes 
last_time_friends and last_time_mentions.

Original comment by tro...@gmail.com on 14 Dec 2009 at 10:58

[GoogleCodeExporter]

> Nowhere :) After starting Pino asks for a complete timeline.

That means, you ask the twitter server?

What happens, if there is another twitter client active at the same time? I 
normaly
use the firefox add-on "Echofon". May be this add-on was active while playing 
with
pino. I'll try this this evening and post you the result.

Original comment by joerg.desch on 14 Dec 2009 at 1:29

[GoogleCodeExporter]

OK, here is my short report. ;-)

If the firefox add-on "Echofon" is running, the "bug" mentioned above occures. 
After
disabling Echofon, pino runs as nearly as expected.

After the startup of pino, the whole timeline is loaded and all new tweets are
colores as "read". After the next update, all new tweets are "unread". In
main_window: refresh_action(), you twee.sync_friends() with last_time_friends. 
After
the startup, this variable is 0. Isn't? Is this the reason why all tweets are 
marked
read? I'm new to vala, so I only can make a guess.

By the way... Pino doesn't show all the unread messages. Is there a limit for 
the
number of tweets in the main window? After a short view into the sources, I 
found
"Soup.form_encode("count", "20")" in twitter_interface.vala. Is this the limit?

Original comment by joerg.desch on 14 Dec 2009 at 8:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I finally understand what you mean. Twitter protocol doesn't has the concept of 
read/unread fields. You can read your timeline from many clients at the same 
time. 
That's why I don't keep information about last recieved tweet between runs.

> Pino doesn't show all the unread messages. Is there a limit for the
number of tweets in the main window
This is limit (or bug) of the Twitter API. It returns even less than 20 last 
statuses 
and ignores this option.

And sorry for my English.

Original comment by tro...@gmail.com on 14 Dec 2009 at 10:30

[GoogleCodeExporter]

> This is limit (or bug) of the Twitter API. It returns even less than 20 last
> statuses and ignores this option.

Ahhh. OK. Now I understand why Echofon uses SQlite to store tweets. ;-)

That behaviour of twitter is really bad. Do you plan a work-around for that?

It's hard to understand why all new tweets got lost, only because of this 
limitation
of twitter.com.

Original comment by joerg.desch on 15 Dec 2009 at 7:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by tro...@gmail.com on 19 Dec 2009 at 4:56

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Forget my comment on identi.ca, I had not seen the button for show older 
entries. Sorry.

Original comment by gege2061 on 25 Mar 2010 at 5:37

[GoogleCodeExporter]

It would be great to see only new tweets when pino is started.

I am not a coder but, I have an idea for that. May be, pino writes the time 
while
updating from twitter server. Then when it starts again, after receiving all 
tweets
from twitter server, it ignores the ones that are older then the time written in
'last update' file and shows only new tweets? Wouldn't it be cool?

Original comment by hsa2%dif...@gtempaccount.com on 28 May 2010 at 7:49

[GoogleCodeExporter]

As far as I remember, the time of the last update is stored by twitter itself 
(on the
server). So pino could fetch this 'last update' time and mark unread tweets on
startup. But it doesn't. IMO that is nearly a show-stopper. :-(

Original comment by joerg.desch on 28 May 2010 at 12:10