gzz-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gzz] Asko 2002-03-07 (AbstractBgVob)


From: Tuomas Lukka
Subject: Re: [Gzz] Asko 2002-03-07 (AbstractBgVob)
Date: Sat, 8 Mar 2003 22:00:00 +0200
User-agent: Mutt/1.4i

On Fri, Mar 07, 2003 at 03:53:51PM +0100, Benja Fallenstein wrote:
> >>>- I'll rewrite my PEG on monday. The new proposition will contain:
> >>> - Bg/border properties optionally in each Vob
> >>
> >>Even in text vobs? SolidBgVobs? Connection vobs? This doesn't sound good.
> >
> >I meant that if BgColor and drawBorder are just two attributes, there is 
> >no need for external AbstractBgVob. So, of course those attributes exist 
> >in only BgVobs, but they are not inherited from any template.
> 
> I don't understand. I am thinking, interface::
> 
>     Color getBgColor();
>     void setBgColor(Color c);
> 
>     boolean getDrawBorder();
>     void setDrawBorder(boolean b);
> 
> and abstract implementation::
> 
>     protected Color bgColor;
>     protected boolean drawBorder;
> 
>     public Color getBgColor() { return bgColor; }
>     public void setBgColor(Color c) { bgColor = c; }
> 
>     public boolean getDrawBorder() { return drawBorder; }
>     public void setDrawBorder(boolean b) { drawBorder = b; }

Uhh, this would be a mutable Vob.

I realized when voiping with Asko that the problem with the bg vobs
is that they're mutable, thus the cloneColored interface.

        Tuomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]