Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

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

The changes to the pro object have to be tracked and use for undoing and redoing actions, skipping and unskipping actions, synchronizing with the server, getting different revisions, and user visualization of the history of an pro object. The user actions are significant changes to a pro object and they should be visible to for the user and editable by him or her. The insignificant changes will be not. Every change should be composed of a set of primitive changes or should be a primitive change. This primitive changes should be serializable and defined.

Task requirements

• Define the primitive changes and list them in the design section.
• Provide interfaces for storing and synchronizing the changes of a Resource.
• Provide a functionality for grouping of primitive changes to the developers.
• Provide a logic that can group changes from different resources to something that can be shown to the user as one significant change.
• Provide interface for redo/undo/skip/unskip (implementation in later revisions).
• Refactor the old code to work for the requirements above.
• Provide a palette the shows the changes to the currently selected book.

Task result

The task result will be source code and palette with the changes to the currently selected book.

Implementation idea

• Use some of the code of the old UndoManager.
• Create special ChangeManager for the Resources, and for the pro object that are in their space.
• Think of an algorithm for global grouping for the user.
• Think of the primitive changes connected to Resource creation and destruction, also entering of a pro object into a ResourceSpace and leaving from it.
• Think of use cases connected to server communication and persistence.

Related

GROUP_RESOURCES_R0? GROUP_PERSISTENCE_R0

How to demo

• Unit tests.
• Demonstration:
  • Run the Sophie 2 author application.
  • Create a new book.
  • Insert a text frame.
  • See in the changes palette the change to this actions for the book...

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.)}