Sync with Google Reader

[GoogleCodeExporter]

User will setup his auth info in options, and check that update will work
as sync with google reader.

When doing update, ask which direction of sync:
- prssr => greader
- greader => prssr

Than do the update.

Original issue reported on code.google.com by and...@gmail.com on 20 Jul 2008 at 11:01

[GoogleCodeExporter]

The lack of this feature is is the primary reason I no longer use PRSS Reader.

Original comment by dalewk...@gmail.com on 3 Aug 2008 at 6:50

[GoogleCodeExporter]

Sure, dale, but nobody else seems to do GReader sync either.  AFAIK, the API is 
out
there, no?  If I can get a toolchain set up to build the source (I have Visual 
Studio
around here somewhere, but not installed), I might take a crack at it my self.

Andrs, thanks for GPLing this!

Original comment by james.bromwell on 3 Aug 2008 at 10:47

[GoogleCodeExporter]

Some info about Google Reader API is on
http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI

Original comment by and...@gmail.com on 4 Aug 2008 at 6:56

[GoogleCodeExporter]

pRSSreader was my favorite RSS reader on my Pocket PC! (the best RSS reader
application for Pocket PC ;-))

But since GoogleReader is available for mobile devices too I am using 
GoogleReader on
my desktop PC and my mobile devices because when I read an item on desktop PC 
it will
be marked as read on the mobile version of course and vice versa. This is one 
of the
important features why I decided to stop using this good reader (on the 
desktop(s) I
stopped using RSS Bandit)

If this feature really comes I'll start using pRSSreader again of course 
because it
brings more comfort for the user than a (good) mobile web page.

Keep up your good work!

Original comment by hfrmob...@gmail.com on 8 Aug 2008 at 9:48

[GoogleCodeExporter]

Dave, I checked out the GR API and it raised a question in my mind: do you
differentiate between "new, unread post" and "marked read, then marked unread"? 
 If
so, it should be possible to do an intelligent 2-way merge of states with GR 
(rather
than having the user pick a sync "direction").  I think that's a more useful 
feature...

Original comment by james.bromwell on 9 Aug 2008 at 11:46

[GoogleCodeExporter]

Yes, it is possible to distinguish between new, unread, read and all of them 
can be
marked (in terms if GReader starred, in terms of pRSSreader flagged).

I might be possible to skip the choose of the sync way. I'm absulutely sure 
that it
will be feasible. Anyway, knowing the way of the sync the algorithm might be 
simpler
(my personal guess, not sure).

Original comment by and...@gmail.com on 10 Aug 2008 at 5:47

[GoogleCodeExporter]

Forgot to add: when implementing this, one should think about more general way 
of
syncing, because sync with Bloglines is also planned - so some sort of plugins 
(not
real plugins) will be a good way and pRSSreader will be easier to extend.

Original comment by and...@gmail.com on 10 Aug 2008 at 5:52

[GoogleCodeExporter]

Surely good idea to sync with Google Reader. I use it daily on my desktop PC. 
Would
be great not to import an OPML files generated by GR into my PPC after changes 
in
subsriptions are made. I vote: Yes.

Original comment by pav...@gmail.com on 19 Aug 2008 at 3:31

[GoogleCodeExporter]

Most of us have a great number of subscriptions to read in google reader but 
only
some of them to read in pRSSreader.

I think it will be useful to be able to choose to sync "All" or "Selected"
tags/feeds. Perhaps, you can use a special tag like "pRSSreader" in google 
reader to
indicate the feeds that should be synchronized.

On the other hand, I have tested for some weeks the "Newsgator" mobile client, 
and I
remarked that it synchronize only feeds that have been changed from the last 
time.
This is useful if we have a big number of subscriptions.

Regards,

Original comment by errais2...@gmail.com on 25 Aug 2008 at 1:02

[GoogleCodeExporter]

The development will be done in greader/ branch. For interested testers and/or
developers.

Original comment by and...@gmail.com on 30 Aug 2008 at 1:54

• Changed state: Started

[GoogleCodeExporter]

See download section for r96 which has a preliminary support for Greader. Also 
go to
prssr-users
(http://groups.google.com/group/prssr-users/browse_thread/thread/bdd5fd1b86d4a44
) for
more notes how to start with it.

Original comment by and...@gmail.com on 31 Aug 2008 at 4:52

[GoogleCodeExporter]

Original comment by and...@gmail.com on 7 Sep 2008 at 12:23

• Added labels: Milestone-Release-1.4.3

[GoogleCodeExporter]

I love this pgm but the new version does not clear cache prior to updating. 
Even 
when u set a max of articles per feed ( and then cut it back ) it keeps the old 
count. Please have a way to clear cache ( it does not seem to work ) ...

Original comment by mpan...@gmail.com on 14 Sep 2008 at 12:10

[GoogleCodeExporter]

Just downloaded "pRSSreader-r127.zip". But about box says Rev126 ...

Original comment by hfrmob...@gmail.com on 20 Sep 2008 at 2:36

[GoogleCodeExporter]

I tried Rev127 for a while (about box says Rev126) but it seems that sync with 
Google
Reader occured only the first time?  (GR --> prssr)

When I read/flag items they are not marked as read/flagged at GR side.

Original comment by hfrmob...@gmail.com on 22 Sep 2008 at 12:58

[GoogleCodeExporter]

Some feeds always appear all marked as read before I've read them.
http://www.colts.com/feed.xml is one that does this. I promise I haven't read 
it in
gReader in while! But it always has them all marked as read in pRSSR when I 
update
the feeds. 

I also am getting a few feeds with too many results, for example weather.com 
gives me
a second copy of all the feeds, and also the quote of the day feed I linked to 
in
issue 82 gives me articles going back to 1 May even though the site never has 
more
than 4 at a time.

I am actually on Rev127 too.

It will be completely awesome when these snags are worked out though! pRSSR is 
the
only one out there that has gReader sync, and that has the amazing offline cache
features for WM.

Original comment by tsuga...@gmail.com on 27 Sep 2008 at 4:35

[GoogleCodeExporter]

Closing this issue, since it was released in 1.4.3. Every other 
issues/improvements
should go to their own issues.

Original comment by and...@gmail.com on 13 Nov 2008 at 4:54

• Changed state: Fixed