Thank you for your comments, kacir. The following words of yours raise some interesting side topics which, on closer inspection, turn out to be more central than lateral:
Quote:
Originally Posted by kacir
... they obviously handed the development to the team that doesn't adhere to fantastic system architecture and specifications set up by the first generation of programmers - the legendary "Guys in Kiev"...
|
I do not know who "they" are or, more importantly, if ever "they" are listening. But if by some stroke of luck "they" happen to listen now, this is what I would like to impart to "them".
MY SIMPLE REQUEST: I would like to have a version of firmware for my recently bought PB Ultra, featuring initially the following core applications: FBReader or CoolReader, Settings, Library, Dictionary, Audio Player; Notes (optional). Nothing else.
My reasoning follows:
A. Whatever implementation you decide on, it should be Open, Simple and Customizable (by this order of importance), as should any self-respecting open-software based box.
B. It should be Open (1) in the sense that it can send and receive data formats relevant to its installed applications. An example: it makes no sense to be able to take Notes while reading, if then one is unable to copy/send them to another device for other functional purposes. Another: a reader app has to outstrip its competitors in the text formats it supports, or in the conversion it affords for dying formats.
It should also be Open (2) in the sense that the file system adheres to widespread standards, that it is not used to purposefully prevent access to the user/owner, and that adequate docs are easily accessible. A reasonable user does not value reliability at the expense of ownership.
It should also be Open (3)in the sense that SDKs should be available for development or adaptation of third party apps, which should be actively encouraged instead of covertly discouraged.
C. It should be Simple (1) so as to avoid the temptation to reinvent the wheel: if there is a Reader App that, by popular consent, fulfils its objectives, it should be ported and improved upon, rather than ditched.
Being Simple (2) also means refraining from adhering to Fashion. ReadRate is a case in point: purports to implement a "reading social network", which is hardly a priority for a device which is used, 99% of the times for 99% of readers, to simply read ebooks in one's placid privacy; did not address functional shortcomings detected in other apps, and in some respects even meant a few steps backwards (see other threads); probably entailed a sizable investment for a very dubious usage base; its usage is not based on its relative merits but on the fact that it is the only one shipped (at least on PB Ultra).
Being Simple (3) also means keeping one's feet on firm ground. If I can flick a page through a simple screen touch on a 6" black and white device which fits in the palm of a hand, what earthly urgency do I have for one or two side buttons? If I can transfer a file simply by copy/paste to a PC, I should not have to waste storage and use Dropbox.
D. Being Customizable (1) means having for a start just the core applications, others being installed according to individual user's whims. For instance: I'd much rather have Python3 installed, than being saddled with progs for which an ereader is not the platform of choice, like browser, dropbox, games, and so on.
Being Customizable (2) also precludes yet another install gui: a simple terminal app using the time-honoured apt-get command line interface does wonders. Proper and thoughtful documentation can give even novices a sense of security.
A system is also Customizable (3) if new and/or groundbreaking apps are first given a whiff of the real world in already stable user environments, for reasons too obvious to need enlarging upon.
That is all for now. Thank you for your time.