home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!portal!cup.portal.com!TomK
- From: TomK@cup.portal.com (Tom R Krotchko)
- Newsgroups: comp.sys.amiga.advocacy
- Subject: Re: The 'Screens' debate:
- Message-ID: <72580@cup.portal.com>
- Date: Tue, 29 Dec 92 18:53:51 PST
- Organization: The Portal System (TM)
- References: <1992Dec24.015546.22863@usl.edu> <72373@cup.portal.com>
- <1992Dec25.033622.2768@usl.edu> <1992Dec29.191135.798@microsoft.com>
- Lines: 29
-
- >MDI = Multiple Document Interface. It is an API for handling
- >an application with multiple documents open at once under once
- >"parent" window. I really don't see how it is like the screen
- >system on an Amiga at all.
-
- >MAIL : IANK@MICROSOFT.COM Crime and Puzzlement
-
- Because, the MDI groups logical screen elements together, exactly
- the way an Amiga Screen does.
-
- This may not be the original intent of Amiga Screens, but that is
- certainly one of their best uses now. In a "single tasking" GUI, its
- pretty obvious that any sort of window that pops up belongs to the
- one task that is running. But in a "many tasking" GUI its confusing
- to a user to have multiple dialogs popping up on the same screen.
- The Amiga Screen eliminates the visual clutter (and confusion) as
- does the MDI.
-
- Incidentally, very few applications make full use of the MDI.
- I've found users prefer when an application is done completely
- within the MDI as opposed to "standard" windows style.
-
- And as I suspected, not everyone within Microsoft fully understands
- how the MDI makes Windows considerably more powerful. The guys writing
- it do, since Win3.1 makes writing MDI apps a snap (I love the way that
- sounds).
-
- TomK@cup.portal.com
- Tom Krotchko
-