Start with the blank slate approach because that allows focus on specific features and functions. Because we've already gone through the mechanical procedures of creating new pages of the card and list types and using the Page Designer to add controls and modify control properties, we won't detail those steps here. However, as you move the focus for experimentation from one feature to another, you may want to review what was covered in this chapter.

Let's walk through some examples of experiments you could do now, then build on as you get more adventuresome. Each of the objects you create at this point should be assigned into an object number range that you are reserving for testing. Follow these steps:

1. Create a new Table 50050 (try using 50009 if your license won't allow 50050). Do this by opening Table 50004 in Table Designer, and then save it as 50050 with the name Playlist Item Rate Test.
2. Enter a few test records into Table 50050, Playlist Item Rate Test. This can done by highlighting the table, then clicking on Run.
3. Create a list page for Table 50050 with at least three or four fields.
4. Change the Visible property of a field by setting it to False.
5. Save and run the page.
6. Confirm that the page looks as what was expected. Go into Edit mode on the page. See if the field is still invisible.
7. Use the page Customization feature (from the drop-down icon on the upper-left corner of the page) in order to add the invisible field; also remove a field that was previously visible. Exit customization. View the page in various modes, such as View, Edit, New, and so on.
8. Go back into the Page Designer and design the page again.
9. One or two at a time, experiment with setting the Editable, Caption, ToolTip, and other control properties.
10. Don't just focus on text fields. Experiment with other data types as well. Create a text field that is 200 characters long. Try out the MultiLine property.
11. After you get comfortable with the effect of changing individual properties, try changing multiple properties to see how they interact.

When you feel you have thoroughly explored individual field properties in a list, try similar tests in a card page. You will find that some of the properties have one effect in a list, while they may have a different (or no) effect in the context of a card (or vice versa). Test enough to find out. If you have some Aha! experiences, it means that you are really learning.

The next logical step is to begin experimenting with the group-level controls. Add one or two to the test page, then begin setting the properties for that control, again experimenting with only one or two at a time, in order to understand very specifically what each one does. Do some experimenting to find out which properties at the group level override the properties at the field level, and ones which do not override them.

Once you've done group controls, do part controls. Build some FactBoxes using a variety of the different components that are available. Use the System components and some Chart Parts as well. There is a wealth of prebuilt parts that come with the system. Even if the parts that are supplied aren't exactly right for the application, they can often be used as a model for the construction of custom parts. Remember that using a model can significantly reduce both the design and the debugging work when doing custom development.

After you feel that you have a grasp of the different types of controls in the context of cards and lists, consider checking out some of the other page types. Some of those won't require too much in the way of new concepts. Examples of these are the ListPlus, List Parts, Card Parts, and, to a lesser extent, even Document pages.

You may now decide to learn by studying samples of the page objects that are part of the standard product. You could start by copying an object, such as Page 22 - Customer List, to another object number in your testing range and then begin to analyze how it is put together and how it operates. Again, you should tweak various controls and control properties in order to see how that affects the page. Remember, you should be working on a copy, not the original. Also, it's a good idea to back up your work one way or another before making additional changes. An easy way to back up individual objects is to highlight the object, then export it into a .fob file (File | Export). The restore method is the reverse, importing of the fob file.

Another excellent learning option is to choose one of the patterns that has a relationship with the area about which you want more knowledge. If, for example, you are going to create an application that has a new type of document, such as a Radio Program Schedule, you should study the Document Pattern. You might also want to study Create Data from Templates Pattern. At this point, it has become obvious that there are a variety of sources and approaches to supplement the material in this text.