WallaRead

Rating: 
5
Your rating: None Average: 5 (2 votes)

WallaRead is a client for Wallabag v2 and above.

With Wallabag you can store articles to read later and synchronize them with your phone in WallaRead. The application works offline once synchronized so you can read wherever you go. Images are downloaded locally and embedded in the articles, so even without data coverage you can still have your full articles at hand.

You can find the application source code on Github. Please report any bugs you find!

Screenshots: 

Keywords:

Application versions: 
AttachmentSizeDate
harbour-wallaread-0.1-1.armv7hl.rpm53.36 KB16/12/2016 - 18:56
harbour-wallaread-0.2-1.armv7hl.rpm55.02 KB18/12/2016 - 13:30
harbour-wallaread-0.3-1.armv7hl.rpm60.45 KB21/12/2016 - 13:09
harbour-wallaread-0.4-1.armv7hl.rpm62.53 KB27/02/2017 - 19:22
Changelog: 

0.4

  • Add an option to download only unread articles
  • Fix a bug where password (and others) were not correctly URL-encoded
  • Add sorting options in the articles list
  • Rework the articles list filtering to limit menu creep

0.3

  • Supports embedding images in articles
  • Adding articles is now supported
  • French translation courtesy of Quentin P.

0.2

  • Fixed synchronization bugs with wallabag.it and maybe other installations
  • Added server deletion from the main page
  • Synchronize articles deleted on the server side
  • Various small bugfixes

0.1

  • Initial release

Comments

joeysys's picture

Please escape '+' in password, or it will return 400.

goestreicher's picture

Thanks for the report! I can confirm it, and it'll be fixed in the next release.

kaulian's picture

Hi,

 

Thanks for this application.

I have 4000 articles most are archived, import never finish :)

I there a possibility to import only unread post ?

 

Thanks

goestreicher's picture

Hi,

Ah, 4000 articles may indeed take quite some time. I'll add an option to only sync unread articles in the server configuration.

Thanks for the feedback!

kaulian's picture

Thanks for the update.

Now i can view my articles

goestreicher's picture

Excellent :) Thanks for taking the time to confirm!

babba22's picture

Hi! Nice work :D but sadly when I try to sync my article it starts an endless loop...

Here are the logs:

$ harbour-wallaread
[D] QWaylandEglClientBufferIntegration::QWaylandEglCl
ientBufferIntegration:62 - Using Wayland-EGL
[D] getDatabase:528 - Opening new connection to the d
atabase
[D] onServerIdChanged:43 - Loading information for se
rver 1
[D] connect:75 - Opening connection for server 1
[D] _sendAuthRequest:213 - Sending auth request to ht
tps://app.wallabag.it/oauth/v2/token
[W] unknown:454 - file:///usr/lib/qt5/qml/Sailfish/Si
lica/private/PulleyMenuBase.qml:454:13: QML State: Bi
nding loop detected for property "when"
[W] unknown:-1 - <Unknown File>: QML StateGroup: Can'
t apply a state change as part of a state definition.
[D] :224 - Auth request response status is 200
[D] onConnectionDone:90 - Successfully connected to s
erver 1
[D] :111 - Downloading articles changes since last sy
nc
[D] _downloadNextArticles:446 - Getting articles at h
ttps://app.wallabag.it/api/entries.json?since=0&perPa
ge=10&page=1
[D] :452 - Articles download status code is 406
[C] showError:63 - Failed to download articles: HTTP
request failed: 406

goestreicher's picture

Hi!

The synchronisation has been fixed in this commit. Testing with wallabag.it also showed some bugs that I didn't get on my own installation, so thanks for pointing me to this instance :)

I'll release 0.2 soon so that you can find other issues or, maybe, read articles :)

babba22's picture

WOW! Great job :D thank you, now it works!!

I hope not to find any more bugs xD but if that happens I'll let you know for sure ;)

goestreicher's picture

Hi!

Thanks for the feedback, and I'm sorry that it's not working out of the box for you :(

Regarding the spinning animation that doesn't disappear this has been fixed in this commit.

For the 406 error this is the first time I see it. I've created an account on wallabag.it and can indeed reproduce this error, so there's hope that I'll be able to track the source down. I'll keep you updated of my progress.

Thanks again for the report!