Quote:
Originally Posted by Godzil
How could you say that ? There are number of products that change externally but still be the same internally. Button position does not mean "need new way to address the buttons" The accelerometer will only need a new driver that activate only if it's present etc... Sorry, but I really don't think they need two separate build since the hardware is pretty much the same...
|
Of course it's possible to activate a driver just when the hardware component is present but I assume there will be some functionality implemented which uses the accelometer. All these functions will have no use in a Cybook and for all functions in the UI which can make use of the accelometer there has to be another version without the accelometer or otherwise the Cybook users could not use that portion of the UI. So basically when using the accelometer you would always have to think: Ok, good. Now, how do we implement that for the Cybook users.
And think of what happens if you have to update the driver for the accelometer or change some code for checking the position of the accelometer: You would always have to do a full test cycle with the 2 Cybook versions before you could release it, even though they are not (and therefore should not) be affected by the change.
Also it's certainly makes no difference where the buttons are places but as far as I could make out on the screenshots the Opus has a different number of buttons and different functionality for the buttons (e.g. the "back" und "menu" is not in the Cybook). This is based on what I saw on a few screenshots so I might be wrong there, in that case disregard the argument :-)