0:12 Notice that as soon as a component is dropped on the workspace it is live. This will be true for the effect of adding or removing a wire. You also see that the tool and the application UI are peers, side-by-side.

0:40 the Text Source component squirts out a string. Notice the effects of connecting it, and then changing the string. Notice also how it is parameterized by (a)selecting it, (b) going down and clicking on a “command”, and (c)filling in and confirming a parameter value. (I hesitated because I didn’t know whether I wanted 3 or 4.) Also notice the “projector” and “projection” language.

1:00 Now I’m going to build a list of four strings.

1:20 Here I add a “probe” instrument, like putting an oscilloscope on a wire. It has its own window, which projects the value it’s monitoring. Follow it as I make changes to the collection.

1:54 “DemoData” is a wrapper that wraps every application data object. In my recent papers I’ve been calling it “Flow Object”.

3:30 Nothing happens when I wire the collection directly to the window frame; I need a projector of a collection.

3:44 All the “Choose One” projectors have a uniform protocol; they’re interchangeable as far as their interaction with the rest of the wiring diagram is concerned.

3:53 As soon as I wire the List Box projector to the Window Frame projector you see its default outline. (It can be parameterized.)

4:05 Yes, it takes clicks, but what about the effect of making a selection?

4:22 the “Selector” component does that. It’s like a rotary switch.

4:51 When we move the probe you will see that the collection going into the projector has an additional member: a (1-based—remember this is Smalltalk) index. See it in the upper right corner of the probe window.

5:27 Now we’ll add a projector to show the selected string.

6:03 Now it gets interesting. I’m going to edit “Shemp” by adding an L at the end. You will see all four projections change.

6:18 The edit is confirmed by the Enter key.

6:29 One of the 4 projections of the string is in the wiring tool. You see that the tool and the application are a single integrated application.

(Note: There might be an appearance of delay even though delays are imperceptible. This is because Windows shows a selection on mouse-down, while the back-end gets the selection event on mouse-up.)