Quote:
Originally Posted by Apocalypto
Faterson it's probably not worth engaging you but try to understand that what you find desirable might not be the same as everyone else.
|
You're not reading my posts carefully, which is par for the course on MobileRead, naturally.
What I'm arguing for is exactly the reverse of what you're suggesting above: do
not shove the same preference down the throats of all Marvin users, but give every Marvin user the freedom to select the preference that suits him or her best.
That's what makes software smart, and that's why Apple software is dumb as a rule, because it practically never offers that freedom. It's to be hoped that Marvin will be
very different from typical Apple software.
Quote:
Originally Posted by Apocalypto
It's easy to throw 80 million preferences and behaviors into an app to try to accommodate everyone but it makes it harder to Kris to develop and maintain, and harder for users to wade through all the options trying to get it to do what they want.
|
Ridiculous line of reasoning.
What can possibly be "confusing" about the availability of a two-fingered gesture that existed in Marvin 1 and Marvin 2 for 5 years? If you don't want to use the gesture, don't use it. No one is holding a gun to your head, forcing you to use features you're not interested in. Kris can disable the two-fingered gesture by default, for all I care. The important thing is for the gesture to remain available in Marvin 3.
Once again, the basic principle:
upgrading software should never, ever result in the loss of trusted and useful features from the previous software version. That's a big no-no and, unfortunately, Marvin 3 violates it in quite a few ways currently.
We can only hope that everything lost from Marvin 2 will be restored in Marvin 3 soon.
Also, any other advanced settings can be conveniently hidden in an "Advanced settings" section, and disabled by default, so that they can't
ever possibly confuse anyone. That line of reasoning of yours is, typically, a false cop-out and lame excuse used by developers when they're unwilling to accommodate user requests for improvement of their software.
Quote:
Originally Posted by slantybard
Is there any way you can specify the colour of a swatch in M3 SxS? For example, I like a background of 80% black (#333333 or RGB 51, 51, 51) in my night mode.
|
It currently isn't possible, but I've been requesting this from Kris for years now. For example, my favourite shade of red is
#990000 and I'd love to use it in Marvin, but because we can't input those hexadecimal (or other) codes directly, it currently isn't possible.