7
What do the terms mean MDI (Multiple Document Interface) and SDI (Single Document Interfaces) regarding the software interface? I read about it, but I’m still confused about the terms, perhaps for lack of examples. What are these patterns?
1 answer
11
What are?
The names say it all. MDI (Multiple Document Interface) translates to Multiple Document Interface as it deals with a choice of interaction method in which an application allows the user to manipulate multiple "documents" in the same session (the same application instance). On the other hand, SDI (Single Document Interface) translates to Single Document Interface because it deals with the choice of interaction method in which the user can only handle a single "document" at a time (or for each instance of the application).
Classic examples are text editors. Notepad, traditional Windows, for example, only allows editing a file:
On the other hand, Notepad++ already allows you to edit several of them at the same time by selecting the asset from tabs (one for each open file):
Note that I previously used the word "document" in quotation marks. The reason is that such a "document" can be anything other than a text file. A music editing app that uses an SDI approach would allow you to edit only one song at a time, while another one using the MDI approach would allow you to edit multiple songs, probably by switching between them through internal tabs or windows. In fact, there are several design standards for MDI applications, and the tabs are just one of them. Previously used internal mini-windows in the window "father" (the main application):
But today it is more common to use "docked" tabs or windows (which can be "docked" in pre-established regions or moved to "float" as independent windows).
What good are they?
When a designer considers using one or another interaction approach, he considers the use that users will make of such "documents". The main question is:
The user will need to simultaneously manipulate more than one file?
If the answer is yes, the option for an MDI approach may be the most appropriate one. I say can because nothing prevents you from allowing users to open more than one instance of the same application and edit each "document" in a separate instance. In that case, an important additional question is:
What will be the interactions between "documents" that the user will need do?
Because if the user needs to interact between documents quite often (for example, looking at something that is in one to decide how to change the other, or copy and paste, etc.), it can make a lot more sense from the usability point of view you provide an MDI interface.
Browser other questions tagged terminology mdi gui
You are not signed in. Login or sign up in order to post.
Great answer, in this case then the internet browser is MDI, and Word is SDI, the purpose of the application can influence in choosing these interface templates. For example, if I create a program that allows you to open several windows, but I can’t access the previous windows until I close my current window, this is SDI?
– gato
Most popular browsers are yes MDI, but there may be some that are not. Word, in its current version, is SDI, but there have been versions of it that was MDI (Microsoft changed it for some reason that they thought important). No, the impediment to accessing or not accessing previous windows has to do with a window opening mode (modal, for example), and nothing to do with with MDI/SDI. The key idea that sets these standards apart is simultaneous document manipulation.
– Luiz Vieira