Talk:Object-oriented user interface

Latest comment: 1 month ago by 27.96.194.5 in topic I really wouldn't consider Windows object oriented

Figures

edit

I think this article about (graphical) user interfaces could benefit from one or more figures. For example, to illustrate the difference between OOUI and traditional/common graphical user interfaces

Strange full stops

edit

Section "Relationship to domain object modelling" contains:

beginning of the project. . .Furthermore, even if

The ". . ." part looks strange. Should it be like that? --Mortense (talk) 23:06, 30 December 2010 (UTC)Reply

Is this page real?

edit

This page is 11 years old now, and has hardly changed in 11 years. And it's still not clear what an object-oriented user interface looks like. No pictures? No comparisons? I went to read about OOUIs elsewhere on the web with some thought of adding content here, but confusion reigns. I couldn't find a straightforward introduction anywhere. All the more reason to put one here. If only someone who understands OOUI could! Most of the references I found were from the 1990s and early 2000s. Is the idea of OOUI obsolete? Unfashionable? --Emrys2 (talk) 14:08, 31 December 2018 (UTC)Reply

I really wouldn't consider Windows object oriented

edit

It's still pervasively a single window GUI where people work in one window space at a time with no credible way to visually switch windows like Mission Control on Mac OS, albeit Windows tried and failed.

Also, where are the symbolic links to actual physical devices other than drives? Every Mac component has a symbolic representation of a physical device in its directory. Windows does not have this at best it has drivers and a device manager still.

This is not the same as a Unix system where you can see in the OS where every literal device and process is symbolically connected to the OS. Until such time as that is verified that Windows is object oriented with a credible reference I'm going to remove that misinformation. 27.96.194.5 (talk) 09:24, 7 October 2024 (UTC)Reply