Classes

This class is meant to act as an “abstract” base class, providing a simple Dictionary datastore that is stored in the UserDefaults in the Application Bundle. It is designed to be reliable, and extremely simple to use. The stored Dictionary would be a String-keyed Dictionary of Any (flexible types). It s up to subclasses to specialize the typeless data. THIS IS NOT EFFICIENT OR ROBUST! It is meant as a simple “bucket” for things like application preferences. It is not an industrial data storage solution. You have been warned. Subclasses could declare their accessors as KVO-style, thus, providing a direct way to influence persistent state. You can also directly observe the .values property. It will change when ANY pref is changed (so might not be suitable for “pick and choose” observation).

This class extends the prefs class to provide persistent prefs storage. This is used across all test harnesses.

This class is the main application delegate.

It is also the “owner” of the driver instance, and acts as the delegate for the driver.

This class controls the main listing screen (the one that displays a list of devices).

This class provides some common tools for all device view controllers.

This class provides some common tools for all view controllers.

The main reason for creating this class was to allow us to interpret settings, and to fix an issue with Interface Builder.

This view will be used for each table cell.

This class controls the device info listing screen (the one that displays a list of device information).

This class controls the main listing screen (the one that displays a list of devices).

This class controls the main listing screen (the one that displays a list of devices).