← Back to team overview

ubuntu-phone team mailing list archive

Re: [Challenge] Ebook reader

 

On Tue, Feb 2, 2016 at 4:55 AM, Christian Dywan <christian.dywan@xxxxxxxxxxxxx> wrote:
The sync branch didn't make it past proof of concept - see https://code.launchpad.net/~uonedb-qt/u1db-qt/syncWithU1 - it basically works but the code needed cleaning up when my time then was increasingly going into UI Toolkit work, and the aforementioned design problems are still unsolved.

I'd be very happy to see this work being picked up if there's enough interest, especially with concrete use cases to solve, as looking back the original API was not written in the best possible way, especially the Synchronizer.

Thanks, Christian! As I said, my intension had been to use this to synchronize reading position across devices. But when documentation didn't emerge and the file sharing service was shut down, I figured it was dead. I don't have time to look at this in any detail right now, but it'll join my long list of things that it'd be nice to do sometime. If and when I get to it, I'll ping you if I have any questions.

On Tue, Feb 2, 2016 at 2:43 AM, Selene Scriven <selene.scriven@xxxxxxxxxxxxx> wrote:
Plain text is, and probably always will be, a thing.

I have quite a few books in plain text format.  They are usually
.txt.gz or .txt.bz2 though.

Epubs are just zipped HTML files, so supporting gzipped text files wouldn't be such a big thing. Another thing to add to my list of things to do in my copious free time.

As for syncing, have you considered doing it via Calibre support?

No, I actually like my users. :) I kid, but Calibre represents the opposite of my philosophy in many ways. If there's something I can do to make life better for Calibre users, I'll try to help. But Beru will never require the use of Calibre.

On Tue, Feb 2, 2016 at 7:04 AM, Sam Bull <sam.hacking@xxxxxxxx> wrote:
How would OwnCloud file sync know how to sync settings and such from
certain apps? That would require a moderately complex and hacky
solution, which I believe would also require making the phone writeable
(not recommended).

Well, I'm sure each app could have a place to let you specify your OwnCloud credentials. Or it may be listed as a service provider. If you wanted to do it yourself, you'd need to break application confinement. As the Open Store shows, you can do that without making the phone writable.

On Tue, Feb 2, 2016 at 8:21 AM, Neil McPhail <neil@xxxxxxxxxxxxxx> wrote:
(1),(2),(3),(4) are really the same problem. Passing data and sharing
information/content between apps and directories is not mature enough yet.
What is the preferred way forward here? Improve the capabilities and
documentation of Content Hub or relax apparmor restrictions to certain
"shared" directories?

I would add (5) to this list as well. Once there's a mechanism for reading / writing outside of silos, I'd image the SD card could be subject to this as well. Maybe I'm missing some wrinkle here?

(6),(7),(8) any input from the people looking after lifecycle management?
Again, will existing frameworks be improved, new frameworks added or
lifecycle management restrictions diluted? Is there an ETA for one or all
of these?

There've been discussion of lifecycle management in the context of GPS tracking apps. Check the archives if you haven't seen them; I forget what the conclusion there was.

(9) I'm not quite following the thread of what is still switched on and
what is switched off

In summary, there is a synchronization service that could be used for this, but it's un-advertised, un-documented, and perhaps unused.

Thanks all for your help,
Robert





Follow ups

References