4 ms·
Another example: When I open two .doc files, I can only have two separate windows or tabs. But I don't need those windows or tabs. What I actually need is just
by berkimbayev 4y ago
Another example:
When I open two .doc files, I can only have two separate windows or tabs. But I don't need those windows or tabs. What I actually need is just two open files on the screen. And some Word functions. From UI perspective, it can be a "function bar" on top of those two files.
If I want to open an image file and Photoshop, currently I can only have a separate Photoshop window. What I actually need is just an open image file on the screen. And some Photoshop functions - a "function bar" on top of that file.
So the visual difference is that you now have 3 different open files and some "function bars" - all in one workspace. And you can arrange or scale your files in any way you want. And you can arrange "function bars" on the screen or hide them.
- simiones 4y agoI don't understand what "files" means to you. If you have two multi-page documents, you have to somehow arrange them on the screen, and you need to show functions to edit/view/[...] either of them. But, whatever you do, you need some kind of borders to understand where one document ends and the other begins, and you need some controls to change the view of each individual document (such as minimizing or maximizing it) and you need a button of some kind to close the document. Then, if we have two documents and floating bars that you can put wherever you want on the screen, it will be completely impossible to tell which bar controls which document (or displays the state of which document), so we should probably put the function bar somewhere in the document container. And, hey presto, we've reinvented the Window, because it turns out to be a really really useful and natural abstraction.