Re: [Fenfire-dev] Mudyc's merge request

[Tuomas Lukka]

> > "PlaneContent"?
> > 
> > We were discussing this piece of architecture but I really
> > don't think this interface and implementation are a good idea.
> > What I meant is that AbstractMainNode should have an extra
> > variable, 
> 
> I don't think that this is very easy to implement since we keep jumping 
> from mainnode to another one. I will try to add argument contentView to 
> AbstractMainNode's constructor.

That sounds reasonable.

> >     --- orig/org/fenfire/fenpdf/actions/eventgrabs.py
> >     +++ mod/org/fenfire/fenpdf/actions/eventgrabs.py
> >     @@ -136,6 +137,12 @@
> >              self.createFlyingNode(vs, self.node, self.ev, self.fenPDF)
> >              self.drewMainNode = mainNode
> > 
> >     +        viewFunction = 
> > self.fenPDF.views.getMultiplexerNodeContentFunction()
> >     +        placeable = viewFunction.f(self.fenPDF.fen.graph, self.tipNode)
> >     +        cs = vs.orthoBoxCS(0, 'TipNode', -1000,50,50, 1,1,
> >     +                           placeable.getWidth(), placeable.getHeight())
> >     +        placeable.place(vs, cs)
> >     +
> > 
> > What in the world does that do? I have no idea what a tipnode is. Could you
> > add some comment explaining what this is.
> 
> With text cloud you will see the final content as a 'tip' (neuvo, vaari, 
> ohjeistus?) in the left-up corner. I try to document it better ,)

What "final content"? I don't understand at all ;)

        Tuomas