Changes between Version 25 and Version 26 of UsabilityIssues
- Timestamp:
- 08/10/09 18:00:27 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UsabilityIssues
v25 v26 6 6 == 0. Introduction == 7 7 8 This page is to focus on broader areas of Sophie 2 functionality which impact product usability.; this page is purposefully not focused on the level of individual tasks. I've focused on several major sections of Sophie's functionality and added use cases to make it clear how these issues will appear in the real world. A subsection (name TK) discusses how well this works in the current version of Sophie 2 and suggests things that might need to change. 9 8 This page is to focus on broader areas of Sophie 2 functionality which impact product usability; this page is purposefully not focused on the level of individual tasks. I've focused on several major sections of Sophie's functionality and added use cases to make it clear how these issues will appear in the real world. 10 9 This page will be expanded as usability testing begins. 11 10 12 11 == 1. Timelines == 12 13 Timelines exist, though much functionality (using them in conjunction with links, audio, and video) is currently missing. How timelines work across pages (how a user would construct slideshows) is still a big shadowy. 13 14 14 15 Importance = high. … … 17 18 18 19 === 1.1. Time-based media on a page === 20 21 Audio and video can currently be put on a page, but fine controls are still missing. 19 22 20 23 (usecase: people want to put a video or audio file on a page and have it work without messing with timelines more than they have to.) … … 27 30 == 2. Page templates == 28 31 29 Importance = high. 32 Importance = high. These still don't work in any reasonable way. 30 33 31 34 Related issues: copying/pasting frames; shared frame/shared content problem. … … 38 41 39 42 == 3. Frames and flows == 43 40 44 Importance = high. 41 45 42 This is essentially the problem of basic users wanting to use text that spans pages. 46 This is essentially the problem of basic users wanting to use text that spans pages. We can currently link text between text frames, but not across pages. 43 47 44 Possibly immense related problem : interaction between flow frames and page templates.48 Possibly immense related problems: interaction between frames flowing across pages and page templates; autocreation & autodeletion of pages. 45 49 46 50 === Current implementation === 47 51 48 Right now we don't have a way to use flows on the same page oracross pages.52 Right now we don't have a way to use flows across pages. 49 53 50 54 === Use case 1: standard book with single flow frame === … … 59 63 == 4. Sophie Server integration == 60 64 Importance = medium. 65 66 There's currently no way to upload a book to Sophie Server from inside of Sophie (or from the web application) which limits its usefulness. 67 61 68 == 5. Book templates == 62 69 … … 73 80 == 6. Anchoring == 74 81 75 Importance = medium. 82 Importance = medium. Anchoring is connecting a frame to a flow in text: so if you have Figure 1, you want Figure 1 to be near the place in the text that references Figure 1, even if you insert text before that, moving Figure 1 back a few pages. 76 83 77 84 === Current implementation === … … 87 94 == 8. Text styles == 88 95 89 (confusion between character & paragraph application.) 96 Currently: confusion between character & paragraph application. This needs to be separated out; we have no current paragraph or character styles. 90 97 91 98 == 9. Bug reporting == 92 99 93 (See [wiki:UserBugTracking my user bug tracking page]. Not sure if this should actually go in here; but maybe the part about reporting in the app goes in from a usability standpoint - this is something we should be getting feedback on.)100 (See [wiki:UserBugTracking my user bug tracking page]. This is okay now. 94 101 95 102 == 10. Resource handling == … … 117 124 === Current implementation === 118 125 119 Can ostensibly import embedded book via Insert > Book menu item; this doesn't seem very functional. This is a better way of embedding a book than the old drag method.126 Can import embedded book via Insert > Book menu item. This is a better way of embedding a book than the old drag method. 120 127 121 Embedded books palette should display embedded books (does it?). 128 Embedded books palette should display embedded books but does not. 129 130 Embedded books seem like they're going to be very slow for large books. 122 131 123 132 == 13. Sophie Reader and annotations == … … 125 134 === Current Implementation === 126 135 127 The current state of the reader app is relatively good: it does what it's supposed to. Annotations don't seem to be working yet, or at least I can't get them to work. Sophie Server integration isn't there, nor are comment frames.136 The current state of the reader app is relatively good: it does what it's supposed to. Annotations mostly aren't working yet, or at least I can't get them to work. Sophie Server integration is there, but comment frames are not. 128 137 129 138 == 14. Publishing ==