Last modified 11 years ago Last modified on 04/02/09 18:09:23


A window is a rectangular portion of the display on a computer monitor that presents its contents (e.g., the contents of a directory, a text file or an image) seemingly independently of the rest of the screen. Windows are one of the elements that comprise a graphical user interface (GUI). Each window has its own Title Bar. When the content is bigger than the visual working area of the window, scrollbars appear. Note that content is defined for specific elements.


The dialogs are windows which have only basic functionality. Dialogs are windows that provide non-editing functionalities (outside of book editing itself) and provide information - opening, saving, information for books, errors, etc. It is not necessary for a dialog to be related to a specific book.

Book desktop

The book desktop is an improvement of the workspace introduced in Sophie1. It is a work background but with the features of a book that has only one page.

  • Desktop covers the whole work area and can be overlapped by flaps.
  • Desktop has its own resources which can be used in other books
  • Resources can be dragged from and to books desktop
  • Minimize all books shows the book desktop
  • Probably timelines won't be needed in the book desktop
  • Scrolling behavior will remain the same as in the other books - scrollbars where needed
  • The Desktop book doesn't have it's own book window - it uses application window as a book desktop.


The flaps hold most of Sophie’s functionality that the user can’t get at through the halos and HUDs. Each flap has tabs in it; each tab has palettes.


Tabs allow for the selection of data sets to be displayed. Data associated with a tab is accessed through a single click of the tab. Tabs may contain one or more palettes. Tabs present a title that is visible to the user (such as "tools", "books", "pages", etc.)


Palettes give control over application or book element features. Palettes are loaded automatically or as modules. Palettes can be unloaded by unloading the corresponding module.

  • Palettes that control by dragging between layout elements
    • Some list palettes allow dragging elements to the Book Desktop or a book window (from resources palette for example)
    • Dragging a page element to a palette is also possible, for saving templates for example
  • Palettes that control by dragging elements inside the palette
    • Some list palettes allow editing by dragging elements inside the palette.
      • Page preview palette - for reordering pages
      • Timeline palette - by dragging timeline entry frame box
  • Palettes that control by other elements
    • Buttons - for example the plug-in configuration palette
    • Fields - some palettes may contain text fields
    • Preview palettes - contain only preview (text or media) and no controls


Buttons trigger specific functionality. This may be

Bound Control

  • A Bound Control gives the on-the-fly changes functionality. This means that changing a property/group of properties is done immediately, without clicking Apply or OK buttons. All of the changes can be undone.
  • Bound controls are part of huds, dialogs ot palettes.


  • Halos are icons that invoke HUDs or some functionality. Different items in Sophie have different kinds of Halos.
  • Halos are showed when an element (book element) is selected. Displaying halos is relevant with what can be done with this element (book element).


  • HUDs are windows that provide information and control for a specific type of object.
  • HUDs are triggered by Halos.
  • HUDs are used for editing page elements