Changes between Version 17 and Version 18 of PREVIEW_MODE_R0


Ignore:
Timestamp:
05/13/09 13:48:37 (16 years ago)
Author:
kyli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PREVIEW_MODE_R0

    v17 v18  
    1010This mode shows the book as it will look like in Reader. This mode is most convenient for reading books. It allows the user to test his links, events, etc. 
    1111 
    12 Note: Preview mode = Reader mode = Test mode. 
     12Note: Preview mode = Test mode. 
    1313 
    1414Author mode = Edit mode. 
    … …  
    2626 '''Here the suggestion is to have a button "Go to preview" instead of checkbox.. this way it will be much more adequate. Decide about the menu.''' 
    2727 
    28 The frame borders are turned off. '''Will they? currently they are not.''' 
     28Frame borders will be visible if they are set so, the page borders will be visible also (all of them). 
    2929 
    3030All menu items related to editing, for example the Insert menu, File->Save, should be disabled. '''Decide how the items will be disabled - whether each item/functionality will watch the current book previewMode option, or someone will disallow book editing.. If every item will disable itself, define which are these items.''' 
    3131 
    32 Some tabs are hidden: Timelines, Resources, Styles '''Define exactly'''. 
     32Some tabs are hidden: Timelines, Resources, Styles '''Define exactly. The flaps should rather be disabled, think about this'''. 
    3333 
    3434On exiting Reader Mode, all such changes are reverted. '''This should be defined more clear - maybe the user wants to see other than the X on the top right corner.''' 
    … …  
    4646 
    4747== Implementation idea == 
    48  * Currently there is a boolean property inReaderMode in org.sophie2.main.view.book.BookView. According to the specification, reader mode is applied to all books, so move it to AppView. '''This should be removed - obsolete''' 
    49  * '''We should use the reader area - it will hide content outside the page borders. Should also be decided whether the page borders will be visible or not. Note: the reader area is not working right now, so it must be implemented, too.''' 
    50  * '''A good idea (maybe) is to move all logic about visibility in the corresponding feature - for example, huds should hide themselves, flaps, palettes also, etc. This way the bookView / readerArea does not need to know about all the visible gadgets and hide them one by one.''' 
     48 * We should use the reader area - it will hide content outside the page borders. Note: the reader area is not working right now, so it must be implemented, too. 
     49 * A good idea (maybe) is to move all logic about visibility in the corresponding feature - for example, huds should hide themselves, flaps, palettes also, etc. This way the bookView / readerArea does not need to know about all the visible gadgets and hide them one by one. Think about adding similar functionality in the scene elements.. 
    5150 * '''more?''' 
    5251