|
i assume by 'windows' you mean 'microsoft windows', because otherwise your comment makes no sense smalltalk has worked this way since at least 01976, but the word they used instead of 'window' was 'view'. see for example steve burbeck's 01992 'how to use model-view-controller' which is describing smalltalk-80 https://www.researchgate.net/publication/238719652_Applicati... > Views are designed to be nested. Most windows in fact involve at least two views, one nested inside the
other. The outermost view, known as the topView is an instance of StandardSystemView or one of its
subClasses. The StandardSystemView manages the familiar label tab of its window. Its associated
controller, which is an instance of StandardSystemController, manages the familiar moving, framing,
collapsing, and closing operations available for top level windows. Inside a topView are one or more
subViews and their associated controllers which manage the control options available in those views.
The familiar workspace for example has a StandardSystemView as a topView, and a StringHolderView
as its single subView. A subView may, in turn, have additional subViews although this is not required in
most applications. so it's not a peculiarity of x-windows; it's how windows/icon/menu/pointer guis have been built since the beginning. (i'd say 'it's how guis have been built since the beginning' but of course sketchpad, grail, nls/augment, and genesys didn't work this way, and they were certainly graphical user interfaces, even if very different in style.) |
Yes of course he did, and you don't have to guess, because the phrase "Windows for example uses" makes Windows a singular noun, compare with "windows for example use". There is no possible ambiguity in the post you replied to.