wiki:UNPLANNED_GRADIENT_PERSISTER

Version 3 (modified by velizar, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

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

A persister for save/load of the gradient of the background should be written.

Task requirements

  • Create persister for the ImmGradient class
  • Create persisters for all other classes used in ImmGradient, who haven't got one.
  • Create Unit Tests.

Task result

The result is source code.

Implementation idea

  • Create ValueRef-s and PropRef-s for all properties and attributes of the ImmGradient class.
  • Create Persister classes for those attributes/properties who haven't got one.

How to demo

  • Create new book, use gradient in the background, save/load it. Check that the gradient is the same as the one before the save.
  • Run the unit tests.

Design

Implementation

Testing

Comments

  • The gradient types (linear and radial) can be written as strings in the storage on save and later the correct one to be chosen on load according to this string. Similar is the situation with CycleMethod. I will provide more details in the design section.
  • We are talking about adding this to the current Sophie book functionality. it is not correct to lose ifnormation about gradient on save/load.