[prssr-devel-ml] Re: Future of pRSSreader

  • From: David Andrs <pda@xxxxxxxxxxxxx>
  • To: prssr-devel-ml@xxxxxxxxxxxxx
  • Date: Mon, 01 Oct 2007 10:38:48 -0600


Joerg wrote:
> Hello,
> nice to hear from you, especially the personal good luck :)
> I'm now using and think it's quite nice, some features needed 
> getting used to, but so far... I really like the caching, up until now I 
> implemented this on my server, so it was caching the feeds I read for me on 
> a regular basis. But as it is neither trivial nor failure proof I really 
> welcome the addition to pRSSreader. Next best thing to sliced bread is the 
> speed with which pRSSreader works now - without (obvious) caching, the feeds 
> still load amazingly fast when they are read from the "disk".
This caching feature required different cache organization and as a side
effect it brought faster loading of feeds, which is very nice :)

> However, I've found some minor issues, but as I'm not sure, whether you want 
> to hear them, I'll just throw everything together in this one mail.
It is the reason, why I give 1.4.0.X for public testing.

> * When viewing any item (message), pressing the center D-Pad button (center 
> button on my navigation pad) will bring up the Pocket IE, but without any 
> page being loaded (the previously loaded site will remain there). I was 
> expecting it would close the current message as it did in the 1.3.x versions 
> or maybe open the online message. Both versions open the selected item when 
> I press this button.
I have find out the following. If the message is cached ('Link to the
article' at the bottom is in bold) the article is opened ok. But if I
try to open an article that is not cached, pRSSreader behaves like you
reported -> it is a bug.

> * Is there any way to revert to the old way of item movement (i.e. pressing 
> "down" at the end of the shown message will do nothing instead of moving to 
> the next one)? I noticed the registry structure is quite different too, so 
> I'm left wondering where the old registry key might be placed now or if it 
> is implemented at all.
Not yet implemented.

> * I can not copy any error message to the clipboard. Although the items 
> offer "copy" and "cut", I cannot paste anything in any application (Notes, 
> any other app with a text field). I'm not entirely certain as to why this 
> happens.
It is bug.

> * After downloading the feed contents, it (presumably) fetches images with 
> the message "jmeno souboru" - am I guessing correctly?
After feed update, pRSSreader is caching images, html and enclosures. My
plan is to have a manageable download queue, where you can cancel items,
reorder them, etc. For know it shows "jmeno souboru" (means file name)
and the number of items that remain to download.

> Some suggestions:
> * It would be great if it were possible to get more detailed errors 
> (possibly when copying them to the clipboard?) than "Invalid feed file". I 
> love that the new message (probably) represent the real error better than in 
> the old version, but I'm currently not at home, so some of the new errors 
> I'm seeing might be caused by the unstable internet connection I'm using here.
I guess that "invalid feed file" error is in this case caused by
unstable internet connection...
Anyway, more detailed errors are planned.

> * It would be great to have an indication (or a column) in the new "Update 
> feeds" view, that shows how long ago a feed was successfully updated (say 
> <1h, 1h, 2h, ..., 1d, 2d, ...)
I will see what I can do with it. I like this idea.


> That's it from my nagging self, you've done a real good job with pRSSreader!
> Best regards,
> Jörg
> --
> pRSSreader development mailing list
> prssr-devel-ml@xxxxxxxxxxxxx
> http://www.freelists.org/archives/prssr-devel-ml
pRSSreader development mailing list

Other related posts: