-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why not use existing ebook readers? #17
Comments
I decided to base OpenSpritz off an epub reading library because I wanted to keep the project lean and allow it to evolve quickly. Though I started with epub reading I think a more compelling use may ultimately be to digest http links. This way you could "share" a webpage to OpenSpritz from your browser of choice. FBReader and Cool Reader are huge projects, and I can't find a public repository for Cool Reader that's been updated in the last two years. FBReader does seem active here on Github, however. I'd encourage you to integrate the OpenSpritz lib module into FBReader! |
The cool reader repo is still going: http://sourceforge.net/p/crengine/crengine/commit_browser There is already spritz plugin for fbreader: https://github.com/clinta/FB-Ospritz/commits |
I would not limit the input to just URLs, since it defeats offline usage. Also accepting raw text as input is crucial in this scenario. I would like also to notice the PR #60, which adds another text sourcing method, also offline-friendly. |
Why reinvent the wheel? I know of at least 2 GPL'd ebook readers for Android (Cool Reader and FBReader). Why not modify one of them to have an OpenSpritz overlay?
The text was updated successfully, but these errors were encountered: