Algr said:
I'm describing the opposite situation: A program open twice on a single machine, presumably working on two different files.
Yes, that's what we're discussing.
Algr said:
My issue was that if a program, (for example a word processor) was designed to open multiple documents at once, why would you instead open multiple instances of the program?
Hang on.
1. It was not granted that we were talking about a program that is
designed to open multiple documents at once. We were really just talking about programs of which multiple instances can be run.
2. Even if we were, it's not like developers just never thought of what might happen if they allowed this functionality. Programs that can run in multiple instances are
designed to play well with others; they keep to their own sandboxes.
Algr said:
The cost is that it seems dangerous to rely on windows not to confuse two programs with identical names and code, by giving files aimed at one to the other. For example getting their scratch files or working data mixed up, thus randomly merging parts of two files.
Sure - if they were designed badly and buggy. And the same can be said for tabbed programs where multiple files are opened by one app: if it's not designed to handle that usage, it will break!
Algr said:
Another problem I could forsee is things not working due to the user not realizing that they have two different instances of an application open. For example trying to use the "clone" tool in an art program from one document to another. If the tool bars are on top of each other, then the user would have no idea why the clone tool was not working. If they were in different places, remembering what identical window went to what document would be an interface nightmare.
This is entirely subjective - a matter of what the user is familiar with.
If a user comes from an environment where one file = one app, then they will be comfortable with tabbing through multiple fully-functional instances of the same app. But they will be flummoxed by the tab structure of multiple files = one app.
If a user comes from an environment with a tab structure and multiple files = one app, then they will be comfortable with tabbing within a single app. But they will be flummoxed by the multi structure of one file = one app.
In other words - to mangle a loose analogy: PC users are as mystified by the illogic of the Mac paradigm** as much as Mac users are mystified by the illogic of the PC paradigm.
**thus, the very raison d'etre of this thread.
Algr said:
That's the only example of it being useful I've heard. It's based on a limitation of the program. I use multiple browsers like this. Having different browser icons makes it easier to understand where I am at at a given moment.
Simply because you're
used to that paradigm.
I
still find myself robotically
alt-tabbing between different facets of my project, forgetting that all the facets are not separate apps, but just different tabs within my browser (
Is there even a kb-combo that lets you cycle between browser tabs?
Maybe...).