Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=BASE_SKINS_COMMONS_R0, 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

Skins define the look and interactions of a visual element. Properties such as size, location, color, keyboard shortcuts and messages to send are all parts of skins.

SkinPart defines a piece of a skin. ElementID refers to a class. propID refers to the property in the element and value refers to the property value.

Skins use properties, so changing skin values at runtime should reflect the change in Sophie.

Annotations are used to define the internalSkin values, @SkinPartDef

Persistence

Skins need to be able to be written to files for the sake of persistence. Skins with media (images) should be stored in an archive.

Naming Conventions

Skins are hierarchical, starting with the InternalSkin, While there is no Sophie restricted naming convention, we should use the following naming convention for our skins:

• The base skin file is the name of the skin, for example, "CoolBlueSkin"
• Any child skins that define language specific parts of a skin should be named <base><language>, for example, CoolBlueSkinEN or CoolBlueSkinBG

Task requirements

^{(List the necessary requirements that the task must fulfill.)}

Task result

^{(List the end product of the task (for example "Source code", "Wiki page", etc.))}

Implementation idea

^{(Provide some rough implementation idea(s).)}

Related

^{(Add links to related tasks that could be useful or helpful.)}

How to demo

^{(Provide instructions for demonstration of the task.)}

Design

^{(Describe your design here.)}

Implementation

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

Testing

^{(Place the testing results here.)}

Comments

^{(Write comments for this or later revisions here.)}