Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=GLOBAL_SPEC_MANAGING_R3, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

The Global specification provides artifacts that can produce useful specification and are very helpful for the analysis and user documentation.

Task requirements

• Implement this task after (or in parallel with) GLOBAL_SPEC_STRUCTURE_R2
• Define global requirements for the different types of elements (flaps, tabs, palettes). Choose where to put them. Collect and fill them in. See implementation idea.
• Fill in the information in the structure created in GLOBAL_SPEC_STRUCTURE_R2
  • In the layout visuals page
  • In the page elements visuals page
  • In the Drag and drop table

Take the prototypes for these from the current specification artifacts listed in GLOBAL_SPEC_STRUCTURE

• For different elements, link related tickets where needed.

Task result

Filled in wiki pages. Migrated artifacts. Expanded and corrected specification where possible.

Implementation idea

Implement this task in parallel with GLOBAL_SPEC_MANAGING_R4 For the palette you can say the elements that it may contain (list, buttons, etc) and default behavior (common behavior). You can put these into the corresponding pages (visuals pages)

Related

GLOBAL_SPEC_MANAGING_R4
GLOBAL_SPEC_STRUCTURE_R2
GLOBAL_SPEC_STRUCTURE

How to demo

Show the resulted pages.

Design

Checked that GlobalSpecification is covered and covers the artifacts

• trunk/sophie2-platform/doc/specification/ files will be linked, but not added for now.
• Copied the folder specification to another non repository location. Will delete moved things in order to make sure all of the information is covered.
• Specification of common elements will be collected here and modified for approval

---

Remove ? for filled sections.

Type

Flap

Description

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.

Diagram?

Tooltip?

Mouse Behavior

Left Clicking the inner border and dragging changes flap's width.
Left Clicking the Minimize button of a flap hides the flap.
Left Clicking the name of a hidden flap shows the flap
Left Clicking the Attach button of a flap detaches/attaches a flap.

Keyboard Behavior

Clicking Tab button when a flap is focused changes the focus to another flap.

Mouse + Keyboard?

Triggered by

Flaps are loaded automatically and cannot be closed.

OS Specific?

Related tasks?

BASE_LAYOUT_R0
BASE_LAYOUT_R1?
BASE_LAYOUT_R2?
BASE_LAYOUT_R3?
APP_LAYOUT_ALTERNATIVE_R0
APP_LAYOUT_ALTERNATIVE_R1?
APP_LAYOUT_ALTERNATIVE_R2?
APP_LAYOUT_MYDOGGY_R0
APP_LAYOUT_MYDOGGY_R1
APP_LAYOUT_MYDOGGY_R2

---

Remove ? for filled sections.

Type

Tab

Description

Tabs are containers for palettes. A tab can contain one or more palettes. Tabs live inside flaps. The size of the tab is the same as the size of flap containing it.

Diagram?

Tooltip?

Mouse Behavior

Clicking a tab name switches to it.

Keyboard Behavior

Clicking Tab button when a tab is selected selects another tab.

Mouse + Keyboard?

Triggered by

Tabs are loaded automatically and cannot be closed.

OS Specific?

Related tasks?

BASE_LAYOUT_R0
BASE_LAYOUT_R1?
BASE_LAYOUT_R2?
BASE_LAYOUT_R3?
APP_LAYOUT_ALTERNATIVE_R0
APP_LAYOUT_ALTERNATIVE_R1?
APP_LAYOUT_ALTERNATIVE_R2?
APP_LAYOUT_MYDOGGY_R0
APP_LAYOUT_MYDOGGY_R1
APP_LAYOUT_MYDOGGY_R2

---

Remove ? for filled sections.

Type

Halo

Description

Halos are icons that invoke HUDs.

Diagram?

Tooltip?

Mouse Behavior?

Left clicking a clickable halo invokes a HUD.
Left clicking and dragging a draggable halo moves halo around to perform various operations.

Keyboard Behavior?

Mouse + Keyboard?

Triggered by

Halos are showed when an element (book element) is selected. Displaying halos is relevant with what can be done with this element (book element).

Related tasks?

See specific halos.

---

Implementation

^{(Describe and link the implementation results here (from the wiki or the repository).)}

Testing

^{(Place the testing results here.)}

Comments

• Please, do not forget the R2 revision of this task during the next iteration. --kyli@2009-02-20