Re: [Gzz-commits] gzz/gzz/view LinebrokenCellContentView.java

[Benja Fallenstein]

Tuomas Lukka wrote:
> On Sat, Jan 11, 2003 at 08:29:04PM +0100, Benja Fallenstein wrote:
>
> > Tuomas Lukka wrote:
> >
> > > On Sat, Jan 11, 2003 at 05:22:47PM +0100, Benja Fallenstein wrote:
> > >
> > >
> > > > Tuomas Lukka wrote:
> > > >
> > > >
> > > > > > How would giving a very long width string (60 times "X") work when the
> > > > > > content of the cell is small? Would LCCV give smaller width if its has
> > > > > > only one short line as its content?
> > > > >
> > > > >
> > > > > If not, it should be made to do it.
> > > >
> > > > I think it looks better if it only expands vertically, not horizontally.
> > >
> > >
> > > Umm, the context here is that the text is there just as text, and if 
> > > there's
> > > a link, a box is drawn.
> > >
> > > In this context, drawing an over-large box is not reasonable.
> >
> > I understand, but the point is that this is not what 
> > LinebreakingCCV/getSize() is *primarily* for. I think that LCCV should 
> > do what looks best for vanishing views, and if other applitudes have 
> > other linebreaking needs, we should have a subclass or something.
>
>
> I think you are putting too much weight on vanishing view and
> the cell-box stuff and that's causing many of our differences here
> (such as the statful VobScene etc).

I don't understand what these have to do with each other.

> What needs to be done is to see what types of linebreaking needs we have
> and create a corresponding class hierarchy. Vanishing is *just one view*
> among  many.

Linebreaking is not done by LinebrokenCellContentView, but 
gzz.vob.linebreaking.

-b.