[Gzz-commits] gzz/doc/pegboard/vob_colorable--humppake peg.rst

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Asko Soukka <address@hidden>    03/03/24 07:08:10

Modified files:
        doc/pegboard/vob_colorable--humppake: peg.rst 

Log message:
        forgotten update

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/vob_colorable--humppake/peg.rst.diff?tr1=1.7&tr2=1.8&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/vob_colorable--humppake/peg.rst
diff -u gzz/doc/pegboard/vob_colorable--humppake/peg.rst:1.7 
gzz/doc/pegboard/vob_colorable--humppake/peg.rst:1.8
--- gzz/doc/pegboard/vob_colorable--humppake/peg.rst:1.7        Fri Mar 14 
09:22:49 2003
+++ gzz/doc/pegboard/vob_colorable--humppake/peg.rst    Mon Mar 24 07:08:10 2003
@@ -5,8 +5,8 @@
 :Authors:   Asko Soukka
 :Stakeholders: Benja Fallenstein, Tuomas Lukka 
 :Date-created: 2003-03-05
-:Last-Modified: $Date: 2003/03/14 14:22:49 $
-:Revision: $Revision: 1.7 $
+:Last-Modified: $Date: 2003/03/24 12:08:10 $
+:Revision: $Revision: 1.8 $
 :Status:   Current
 :Scope:    Trivial
 :Type:     Feature
@@ -36,11 +36,11 @@
 - Why is Abstract Colorable Vob needed?
 
   RESOLVED: Currently there is no common interface for multiple solid
-  colors in vobs, but they are defined and implemented from the scratch in 
-  every background vob (starting from ``RectBgVob``). A common interface is
-  necessary when a single node view that supports solid colors, should
-  select between multiple different background vob types (basing the
-  selection i.e. on nodes' content).
+  colors in vobs, but they are defined and implemented from the
+  scratch in every background vob (starting from ``RectBgVob``). A
+  common interface is necessary when a single node view that supports
+  solid colors, should select between multiple different background
+  vob types (basing the selection i.e. on nodes' content).
 
 - Why was the PEG for Abstract BackgroundVob declared irrelevant?
 
@@ -165,6 +165,12 @@
   They could be implemented as shorthands to the cloneColored(color[])
   method. I.e. ``return cloneColored(getColors().clone().append(color))``.
 
+  RE-RESOLVED: *The default action* of cloneColored() should be adding
+  new colors in addition to the already existing colors. Therefore
+  cloneColorAdded() methods will be renamed to cloneColor() and methods
+  cloning with only colors provided as parameter, will be renamed to
+  cloneColorReplace().
+
 - Should SolidBgVob be inherited from Colorable Vob?
 
   RESOLVED: No. ``SolidBgVob`` is not a such background vob than other
@@ -209,9 +215,9 @@
            +ColorableVob cloneColored(Color[] colors)
            +ColorableVob cloneColored(List colors)
            +ColorableVob cloneColored(Color c)
-           +ColorableVob cloneColorAdded(Color[] colors)
-           +ColorableVob cloneColorAdded(List colors)
-           +ColorableVob cloneColorAdded(Color c)
+           +ColorableVob cloneColorReplace(Color[] colors)
+           +ColorableVob cloneColorReplace(List colors)
+           +ColorableVob cloneColorReplace(Color c)
            +Color[] getColors()
    
     class java.lang.Cloneable "interface"