[Pipet Devel] NetInputs and NetOutputs

J.W. Bizzaro bizzaro at geoserve.net
Mon Jun 19 12:02:51 EDT 2000

Brad Chapman wrote:
> Subnets, which are equivalent to composite loci in Loci.

For Piper, we should probably just stick to Overflow's terminology of
"networks" and "subnets".

It goes to show how compatible Overflow and Loci concepts were.

>         Now, the question is, what is the process by which we will direct
> the input from the Constant into, say, input connector 1 of the NetExec.
> Similarly, how will we direct the output of say, output connector 1 of the
> NetExec into the TextViewer?

I'm not sure if you're asking how this can be done conceptually or graphically
(in which case, I can answer the question), or how this can be implemented (in
which case, Jarl should answer the question).

>         I am not sure at all how this is concieved to work in GUI, so I'm
> having a hard time visualizing how to model it in the definition layer.
> Does anyone have any ideas about how to do this, so that I can get a better
> grasp on what do ? Thanks much!

Conceptually and graphically, it's very simple: Unconnected pipes in a subnet
mean the I/O is redirected from/to the parent network.  In Pied/Piper, all
"dangling" pipes are reproduced at (mapped onto) the parent node's icon (this
is not implemented yet).  To "close" a pipe or create a "dead end", the user
must "hide" it (also not implemented).  In Peep, the user will need to issue a
"close" or "cap" command to do the equivalent.

In your screenshot/mockup, you show the subnet containing a node with 4
unconnected pipes (2 in and 2 out).  When Pied is working properly, ALL 4
PIPES will be mapped onto the parent node's icon.  You are only showing 2
pipes on the parent (1 in and 1 out).

The unconnected pipes should also have names, as Jean-Marc suggested, which
will help the user see what pipe pipes what kind of data (not implemented
either!).  I need to get to work :-)

                      |           J.W. Bizzaro           |
                      |                                  |
                      | http://bioinformatics.org/~jeff/ |
                      |                                  |
                      |        BIOINFORMATICS.ORG        |
                      |           The Open Lab           |
                      |                                  |
                      |    http://bioinformatics.org/    |

More information about the Pipet-Devel mailing list