Quote:
Originally Posted by kguil
@tomsem I've thought about MDI a lot when designing M3. Many devices that Marvin is expected to run on don't have enough resources (memory mostly) to run MDI. There are also some reading modes that are 'logically' inconsistent when running together e.g. vertical auto scroll one book and text to speech on the other that make the proposition rather complex. This complexity could also translate into a more cluttered UI for the majority of people who wouldn't be interested in the feature.
|
One example I forgot about is Goodreader. It uses tabbed views (only one at a time), but you can switch documents quickly, and there's a way to Duplicate a tab so you can have multiple views of the same document. 'File Tabs enabled' is a preference, enabled by default I think (at least on iPad), the only reason they suggest one might want to turn it off would be to conserve 'precious screen space' (when reading options, including tabs, are displaying). A single-view-at-a-time implementation like this would not introduce complexity about scrolling or TTS, but would confer quick-switch ability.
If tiled windows is too resource intensive it could perhaps be restricted to newer devices with more RAM to work with. But then the other UX issues you mention would need to be addressed.