search

KyubiSystems / Wisewolf

Web-based RSS newsreader, with additional image-handling features. Replacement for Google Reader.
GNU General Public License v3.0
6 stars 0 forks source link

Coldsweat and Wisewolf: a lot in common #5

Open passiomatic opened 10 years ago

passiomatic commented 10 years ago

HI there,

I'm opening an issue since I didn't find an email address to write to. I'm the author of Coldsweat - yet another Python RSS aggregator. I noticed you starred Coldsweat a while ago so I've taken a look at Wisewolf.

I was wondering if you have a clear idea on how to extract/use images found in feeds, It's definitely a nice feature which I was pondering to implement myself too. I believe I've seen first in Feedly - you know in the "grid view".

Coldsweat actually has a grid view (see screenshot), used only in the feed list for now, but I can see one could fit the (first?) image found in the feed entry within each box.

screen shot 2014-02-08 at 15 48 37

The more complex part - I think - is to extract such image, scale it, and put it somewhere in a cache to reuse it when needed.

More generally I believe there's a lot of overlap between the two project and you are welcome to open issues/contribute/fork/whatever.

Thanks.

KyubiSystems commented 10 years ago

Thanks for your comment. The image extraction would probably be done by whatever's easiest, a parsing library like Beautiful Soup to extract the image urls, urllib3 to fetch, and Pillow to resize the images. The caching layer should be pretty simple to implement.

Wisewolf is mainly a way of teaching myself asynchronous network programming and websockets, and to scratch an itch. If other people find it useful, that's just a bonus.

passiomatic commented 10 years ago

Thanks for your comment. The image extraction would probably be done by whatever's easiest, a parsing library like Beautiful Soup to extract the image urls, urllib3 to fetch, and Pillow to resize the images. The caching layer should be pretty simple to implement.

Thinking again about caching, a rough implementation could be simply a cache/thumbnails folder with a series of scaled down images 1.jpg, 2.jpg... n.jpg where the number is the ID of the entry. The folder will grow big soon, tough. Anyway Thanks for your input.

KyubiSystems commented 10 years ago

Thinking again about caching, a rough implementation could be simply a cache/thumbnails folder with a series of scaled down images 1.jpg, 2.jpg... n.jpg where the number is the ID of the entry. The folder will grow big soon, tough. Anyway Thanks for your input.

Yeah, that would work.. or you could have one subdirectory per feed, to make things a bit less cluttered, e.g. cache/thumbnails/[feed id]/ containing thumbnails keyed to the individual post id.