Let's now see what else the Delphi IDE is consisted of.
Before I go into detailing other sections of the IDE, select the second tab near the "Welcome page" - the one named "ConvertItUnit".
No, don't bother with what do you see below the tab. Let's concentrate on the other parts of the IDE.
What is a Delphi program made of?
Let's try with a quick and dirty (read: "I cannot explain all at once") approach...A Windows program created with Borland Delphi will at least have one window - let's call this a form.
A form will contain several controls or components, you know : buttons, tabs, drop down selectors, status bar, etc.
Some controls will be child controls to other, for example a button on a region (let's call this "panel") is a child to this panel and a form is a parent to this panel.
Thus, we have a structure - where any object you work with is in some hierarchical relation to some other object.
Structure
The Structure View shows the hierarchy of source code in the Code Editor, or components/controls displayed on the Designer.Structure is shown in a tree-view like display.
Try clicking on something in the "Structure" window. Note how various parts on the "form" get selected.
If your code contains syntax errors, they are displayed in the Errors folder in the Structure View. You can double-click an error to locate its source in the Code Editor. Of course, there are no errors in the Convert it demo application (if there were error you would not be able to run it).
As you will witness in a second, the Structure, Object Inspector and the Form Designer / Code Editor work cooperatively. If you have an object on a form and click it, its properties and events are displayed in the Object Inspector and the component becomes focused in the Structure view.
