[Pipet Devel] Baby-BL implementation

Jean-Marc Valin jean-marc.valin at hermes.usherb.ca
Tue Sep 12 12:05:12 EDT 2000

> > 1. It seems like this requires that the MBL be smart enough to know that
> > it needs to split a network at display nodes, so that it have access
> > to the results that need to be displayed. So if we we had Jean-Marc's
> > famous A->(B->C)->D network and say C were a viewer that needed to get
> > results, then the MBL would have to know to split the network here and
> > call getOutput on C (before calling on D), so that is could have the
> > output for display. Is this right, or am I way off base?
> I think you're on track, but I dont really get this "a viever halfway a
> network". I always
> though every network has just one input on the start and one viewer at the
> end of a
> nodes network?

viewers are a totally different thing (you haven't seen one yet). Viewers are
nodes that take their input and send that to the GUI to display it... then they
return the same object as their output. They're bypass nodes with the side
effect of displaying the value in the GUI (mostly for debugging). So viewers
have nothing to do with the "end nodes".

> > 2. I'm not sure how the Overflow *Probe will work under this system. Am I
> > missing something basic?
> >
> The "*Probe" system? Please explain.

Probes are a bit like viewers, debugging nodes. You insert them in the middle of
your network and they allow you to trace the flow. They make next/continue/stop
buttons appear on the GUI.


Jean-Marc Valin
Universite de Sherbrooke - Genie Electrique
valj01 at gel.usherb.ca

More information about the Pipet-Devel mailing list