cs427-23

cs427-23 - 1 UI Implementation CS427 23-2 More from Joel...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 1 UI Implementation CS427 23-2 More from Joel Design for people who have better things to do with their lives Text? Mice? Memory? CS427 23-3 Implementation concerns Simplicity Safety Use standard libraries/toolkits Separate UI from application CS427 23-4 Simplicity Don't compromise usability for function. A well-designed interface fades into the background. Basic functions should be obvious. Advanced functions can be hidden. CS427 23-5 Make controls obvious and intuitive Is the trash-can obvious and intuitive? Are tabbed dialog boxes obvious and intuitive? Is a mouse obvious and intuitive? CS427 23-6 Safety Make actions predictable and reversable Each action does one thing Effects are visible User should be able to tell whether operation has been performed Undo CS427 23-7 Use standard libraries Dont build your own! If necessary, add to it, but try to use standard parts instead of building your own. CS427 23-8...
View Full Document

Page1 / 21

cs427-23 - 1 UI Implementation CS427 23-2 More from Joel...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online