7 |
:Date-created: 2003-03-05 |
:Date-created: 2003-03-05 |
8 |
:Last-Modified: $Date$ |
:Last-Modified: $Date$ |
9 |
:Revision: $Revision$ |
:Revision: $Revision$ |
10 |
:Status: Incomplete |
:Status: Irrelevant |
11 |
:Scope: Trivial |
:Scope: Trivial |
12 |
:Type: Feature |
:Type: Feature |
13 |
|
|
30 |
Issues |
Issues |
31 |
------ |
------ |
32 |
|
|
33 |
|
- Why is AbstractBgVob needed? |
34 |
|
|
35 |
|
RESOLVED: Currently there is no common interface for multiple solid |
36 |
|
colors in node vobs, but they are defined and implemented from the scratch in |
37 |
|
every background vob (starting from ``RectBgVob``). A common interface is |
38 |
|
necessary when that a single node view could select between multiple different |
39 |
|
background vob types depending on nodes' content; the same node view could place |
40 |
|
different vob depending on the node's content. |
41 |
|
|
42 |
|
RE-RESOLVED: AbstractBgVob will be replaced by AbstractColorableVob |
43 |
|
defined by a new PEG_. This PEG will be declared irrelevant. |
44 |
|
|
45 |
|
.. _PEG: ../vob_colorable--humppake/peg.gen.html |
46 |
|
|
47 |
|
- How should AbstractBgVob features be assembled? |
48 |
|
|
49 |
|
RESOLVED: Background Vob implements interface for single color |
50 |
|
backround and border from Background Interface and handling of |
51 |
|
multiple background colors from Colored Interface. |
52 |
|
|
53 |
- How should the new interfaces and classes be named? |
- How should the new interfaces and classes be named? |
54 |
|
|
55 |
RESOLVED: **public interface Background**, **public interface |
RESOLVED: **public interface Background**, **public interface |
100 |
Colored** and **public abstract class AbstractBgVob** should be |
Colored** and **public abstract class AbstractBgVob** should be |
101 |
created after the following diagram: |
created after the following diagram: |
102 |
|
|
103 |
.. UML:: backgroundvob |
.. UML:: abstractbgvob |
104 |
|
|
105 |
jlinkpackage gzz.vob |
jlinkpackage gzz.vob |
106 |
|
|