Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions

[Tuomas Lukka]

On Sun, Jul 06, 2003 at 10:34:14PM +0300, Matti Katila wrote:
> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> > Matti Katila wrote:
> >> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> >>>The failure of taking this into account means that there cannot
> >>>be transclusions of a node, i.e. one node cannot be placed
> >>>on multiple papers; in Fenfire, transclusion must be supported
> >>>for *anything*, i.e., whenever some thing is in a "context,"
> >>>it must be possible to place it in more than one context.
> >>>
> >>>In order to make nodes transcludable, the vocabulary
> >>>must be changed.
> >> 
> >> Making clones is something what I wouldn't do in word-processing.
> >> Same with pictures. If you are talkking about mindmap thing we should not 
> >> mess it up with canvas2d which is "making notes" - not "making clone 
> >> notes".
> >> 
> >> If you really want to do clones, you also need to make a new api for it 
> >> (similar like ppactions) because pp should not do a such thing.
> >> 
> >> CanvasView2D can be programmed to render also these clone notes.
> > 
> > 
> > We have discussed this at length on IRC, without coming to an agreement. 
> > Here's my summary (keep in mind that it's from *my* POV):
> > 
> > - Mudyc agrees that transclusion of nodes is needed for some things, 
> > e.g. mindmapping, but not for some other applications of 2D canvases, 
> > such as 'general "text"'.
> 
> And my biggest point is that user should recognize if node is clone or 
> not, on canvas. 

Actually, one thing I recently realized is that clones are dangerous,
*if* the user interface doesn't show all the other contexts into which
something has been cloned.

If it does, no problem.

        Tuomas