Changes between Version 9 and Version 10 of UIGuidelinesForShift


Ignore:
Timestamp:
05/08/09 21:59:44 (16 years ago)
Author:
danvisel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • UIGuidelinesForShift

    v9 v10  
    1010== 1. Aspects of the Sophie UI == 
    1111 
    12 (Most of this is based on sophie_v2.pdf.) 
     12(Most of this is based on sophie_v2.pdf; a lot of this is based on parts of the Sophie UI that weren't touched on in that document that need to be addressed.) 
    1313 
    1414=== 1.1. Graphic look & feel (general) === 
    1515 
    16 I think the graphic look is generally good & we like it. 
     16I think the graphic look is generally good & we like it.  
     17 
     18One basic problem is in list palettes: we need to have a general idea of how all list palettes should work, not a bunch of different palette designs that behave in different ways.  
    1719 
    1820=== 1.2. Interactions (general) === 
    … …  
    3638The way timelines were done in Sophie 1 wasn't wonderful and could probably be reworked.  
    3739 
     40One issue: in Sophie 1, every frame on a page had a timeline halo that was dragged to the timeline to move the frame to the timeline. (The frame itself wasn't dragged because the author presumably had positioned the frame on the page first.) This got the job done but it was confusing: most of the other halos did not behave in this way. 
     41 
    3842=== 1.5. Embedded books === 
    3943 
    40 The way embedded books were handled in Sophie 2 - particularly the editing of embedded books - was confusing and needs to be rethought. 
     44The way embedded books were handled in Sophie 2 - particularly the editing of embedded books - was confusing and needs to be rethought. (This has not been implemented in Sophie 2 yet.) 
     45 
     46The main issue here is the problem of focus: you can have two books on the screen at once. In the Sophie 1 design, there was confusion because it wasn't clear what the status bar controls referred to (almost always the parent book, I think) and what the content of the palettes referred to (usually the selected book).  
    4147 
    4248=== 1.6. Page templates === 
    4349 
    44 The idea of page templates is confusing to a lot of people; a good way to implement this that would be quickly  
     50The idea of page templates is confusing to a lot of people; a way to implement this that would be quickly understandable would be fantastic. In Sophie 1, users ended up having to spend a lot of time in the page structure palette figuring out which elements on the page were part of the page template 
    4551 
    4652=== 1.7. Reader application ===