In this section, we are going to discuss how style definitions can be stored, embedded, and manipulated both at design time and runtime.
The StyleBook component has exactly this aim. It is a non-visual component you usually drop onto a form and edit through its component editor (double-click on the component to activate it), that is, the Style Designer we have seen previously. All functionalities related to style persistence (load/save from/to a file) are available at design time and at runtime. If you load one or more styles in TStyleBook at design time, data will be stored within the FMX file of the form the component is on. Keep in mind that styles (especially bitmap styles) can be large in size and they actually get compiled into the binaries of your application.
Every FMX form has a StyleBook property that you can use to instruct the style selection mechanism to look up in a specific StyleBook when looking for style definitions of components on...
