View Single Post
Old 09-24-2013, 03:55 PM   #44
JoeD
Guru
JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.JoeD ought to be getting tired of karma fortunes by now.
 
Posts: 895
Karma: 4383958
Join Date: Nov 2007
Device: na
Quote:
Originally Posted by Katsunami View Post
That's fine with me, but in my opinion it doesn't fly. Not the way they're presenting it.

You can't say "I don't like this piece of software [Calibre] because it doesn't work like I want it to work, and it doesn't do what I want it to do", and then turn around and use that exact piece of software to get your own product started. To make matters worse, that new product is not open source. In my view, that's just opportunistic and very lame.
Sure you can. They didn't say everything about calibre was bad and didn't work/do what they want. Taken as a whole package it doesn't work how they want or in the way they want it, individual elements though may be fine.

So they've written their own software that does what they want, the way they want it and they've used calibre for the bits where it does do what they want in a way that's usable from their app. Which would be the conversion since it's usable via invoking with cmd line args.

If their long term plans are to have a mobile or tablet port of their app, then that'll be one reason why even the conversion side of calibre will be dumped. GPL isn't really compatible with the iOS store for example and invoking other apps then getting the result back isn't afaik possible on at least iOS, not sure about android?

I really see nothing wrong with the approach they've taken.

As it happens, I'd prefer it if calibre didn't take over my folder structure too. However, I understand why the developer chose to do this and I'm interested in seeing how the bookONO developer will work around the issue of outside changes to the folder structure that the app doesn't know about.

Certainly doable, but will likely hit similar issues to those faced by iTunes users who keep music in a folder outside iTune's control.

The only bit I do take issue with is the reviewer, who said it's more open, when the truth is quite the opposite. Calibre is open source, bookONO isn't as yet and according to a quote above from the author, probably won't be. It's an odd statement really.

Last edited by JoeD; 09-24-2013 at 03:57 PM.
JoeD is offline   Reply With Quote