| 2 | | * Each extra should provide its own palette. |
| 3 | | * All created book extras should be listed in the Book Extras palette. |
| 4 | | * there must be either visual marker or label that shows whether the extra is visible or not |
| | 2 | * All created and loaded book extras sets should be listed in the Book Extras palette. |
| | 3 | * there must be visual marker that shows whether the extra is visible or not (e.g. colored are visible and black/white are hidden, see the schematics) |
| | 4 | * Each set is exported to different file |
| | 5 | * One set can contain different types of extras (e.g. one set can contain stickies and highlights) |
| | 6 | * The sets are displayed in the order they've been created/imported. |
| | 7 | * On the top are the first created/imported sets. |
| | 8 | * In each set the extras are ordered by type and order of creation (not modify). |
| | 9 | * In the current set buttons for creating new extras must appear, these buttons must be presented only on the current set. |
| | 10 | * At the top of all sets a buttons for new extras must be presented |
| | 11 | * If the user chooses to create new extra from there it is created in new set, to add extra to some of the other sets the user must first selected it and then to use the buttons for new extra which will appear |
| | 12 | * In the scenarios mentioned above, the "add new annotation set" button is unnecessary. |
| | 13 | * We also may need to consider different file extension if we plan to store different type of extras in one file, because the current .anno.s2 extension will be inadequate. |
