Re: [gzz] Abstract Colorable Vob

[Tuomas Lukka]

On Fri, Mar 14, 2003 at 11:32:25AM +0200, Asko Soukka wrote:
> Thu, 13 Mar 2003, Tuomas Lukka wrote:
> > > Currently, yes. Without this, it wouldn't be possilbe to drop off colors 
> > > from vob primitive. Again, cloneColored(Color) could be a shorthand for
> > > getColors()+addcolor+cloneColored().
> > > 
> > > Should we have List getColorsList() in addition of Color[] getColors()?
> > 
> > We could also have cloneColorAdded()
> 
> Hmm... Benja wants that the default action is adding colors next to the 
> colors of the original Vob. So, following shouldn't replace the existing 
> colours.
> 
>     ColorableVob cloneColored(Color[])
>     ColorableVob cloneColored(List);
>     ColorableVob cloneColored(Color);

I disagree; cloneColored sounds to me like "clone this, but with these colors".

> But they could be shorthands to methods, which would
> have an override flag. When flag is set, old colors will
> be replaced when cloning, if unset, the new colors
> will be added next to old ones. ?
> 
>     ColorableVob cloneColored(Color[], boolean)
>     ColorableVob cloneColored(List, boolean);
>     ColorableVob cloneColored(Color, boolean);

This is not good: no-one will ever remember which one is which.

        Tuomas