I went to Star Wars I because I knew there'd be lightsaber fights in line. I was right. Got there 2 hours before the preview, and watched Reservoir Dogs on my Laptop's DVD with six other people I didn't know in my general vicinity.
It was a _fun_ time, definitely not a _waste of_ time.
Whereas objects are a convenient way for programmers to organize things, they are not a natural abstraction for an end user. Creating a UI model that matches the implementation model is almost always a mistake.
If a user wants to create a document, they should be able to "create a document", not "create an object which has document-specific properties".
A good example of a UI model that matches an implementation model is the UI for file systems. Lots of users that I know throw everything on their desktop because they can't handle understanding a file system. Furthermore, who's to say they're wrong or "messy" for doing it? Current day UIs for file systems suck because they directly reflect the implementation model instead of a model that users are more natural with (such as a document stack interface).
Slashdot Mirror
I went to Star Wars I because I knew there'd be lightsaber fights in line. I was right. Got there 2 hours before the preview, and watched Reservoir Dogs on my Laptop's DVD with six other people I didn't know in my general vicinity.
It was a _fun_ time, definitely not a _waste of_ time.
Whereas objects are a convenient way for programmers to organize things, they are not a natural abstraction for an end user. Creating a UI model that matches the implementation model is almost always a mistake.
If a user wants to create a document, they should be able to "create a document", not "create an object which has document-specific properties".
A good example of a UI model that matches an implementation model is the UI for file systems. Lots of users that I know throw everything on their desktop because they can't handle understanding a file system. Furthermore, who's to say they're wrong or "messy" for doing it? Current day UIs for file systems suck because they directly reflect the implementation model instead of a model that users are more natural with (such as a document stack interface).