search

amyjko / user-interface-software-and-technology

A book surveying the literature on user interface software and technology.
57 stars 8 forks source link

Interactive: student critiques #22

Closed amyjko closed 5 years ago

amyjko commented 6 years ago

This particular chapter echoed what I first learned about the internet and computers in undergrad, but in a more thoughtful and engaging voice. I thought introducing Xerox PARC in an earlier chapter helped brought context into WIMP.

When introducing all of these different interactions of scrolling, window placing, clicking on icons and menus, etc. I think it would be helpful visually if there were accompanying gifs. Not an overwhelming number, but enough to get confirmation of what was read to our mental model of it. For example, I'm not familiar with what a "floating dialog" looks like so having an image support some of the less known tools would be helpful. I know there's the All the Widgets video, but glancing and getting it in under a second helps.

I wish there was more to the copy and paste paragraph. I found this topic so interesting (and ended up reading one of the papers) that I wanted to read more. It was rather unsettling to end the chapter with that like you saved the best bit for last. Maybe placing it before the direct manipulation section which is already a topic covered to help smooth out the conclusion?

amyjko commented 6 years ago

More comments:

The Interactive Interfaces chapter described the now ubiquitous WIMP elements that provide computing systems with direct manipulation paradigms. As I read, I wondered whether readers unfamiliar with non-WIMP systems would understand the contrasts being drawn. When I first started programming in high school, non-WIMP interfaces felt completely alien to me -- and I imagine that's even truer today for people immersed in contemporary OS. Visual examples of linux or other command line interfaces at different action states would help contrast this their WIMP counterparts.

I really enjoyed the models this section used to describe what information problems each WIMP element solved, and wanted further exploration. For example, menus provide a visual for lists of available commands, and they also solve the problem of stepping up and down layered list hierarchies in a few quick gestures. Hearing more about the way each WIMP element maps back to underlying HCI needs would have been helpful. I can think of some examples myself, but I'm sure you have a fuller picture!

amyjko commented 6 years ago

I think in general, I always seem to be looking for headers for some of the topics you write about. For example, the paragraphs that describe window managers, icons, menus, and widgets could benefit from the use of headers. I see your writing as something I would refer back to, so perhaps having a Short list outline at the top or on the side would be very useful to quickly reference something. Also, I really enjoyed the sketch diagram you incorporated in the next reading (architecture), and I would find these useful throughout more of your writing. These simple diagrams are the easiest way for me to fully remember and visualize a concept.