gzz-commits
[Top][All Lists]
Advanced

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

Re: [Gzz-commits] gzz ./TODO gzz/util/Filer.java


From: Tuomas Lukka
Subject: Re: [Gzz-commits] gzz ./TODO gzz/util/Filer.java
Date: Tue, 17 Sep 2002 09:16:04 +0300
User-agent: Mutt/1.4i

> >>>+    a lot right now (Tjl needs to decide how to save
> >>>+    Xanadu links (that's right, *links*, not transclusions)).
> >>>
> >>>     
> >>>
> >>Something wrong with implementing them as two cells linked along a 
> >>special dimension?
> >
> >Searching and the fact that we *don't* want to magick it so that those
> >cells don't show up as transclusions; but they really shouldn't show up.
> >
> >I've implemented a trivial index and am thinking of saving them in 
> >*another* space, to avoid the problem above.
> 
> I think that would be good; I know that there's a tradeoff here, but I 
> feel doing magic below the gzz level is not such a good idea, either... 
> so I'd opt for taking this way before the demo, and think more later.

I think that this *might* be the way after the demo as well: who says
everything has to be in the same zz space.

> OTOH, if you really want to save in Storm for now, you should use 
> Storm/mediaserver directly for now, I think (Filer is only to save 
> Versions of something that is updatable, and usually diffable).

Hmm. Could you take a look at this? I could take the line-breaking text 
and beam stuff (I figured out how to draw nice beams with alpha with the
stencil buffer, so that irregular-shaped beams still look ok) if you could think
about saving. 

Need to be able to save both space and xu links.

        Tuomas




reply via email to

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