Classes

This class functions as a cell that, given an array of objects, will generate an SCArrayOfObjectsSection detail view that’s displayed when the cell is tapped.

The cell can also be optionally bound to an object and generate an additional SCObjectSection detail view when the cell is tapped while the table is in edit mode.

This class functions as a table view model that is able to represent an array of any kind of objects and automatically generate its cells from these objects. In addition, ‘SCArrayOfObjectsModel’ generates its detail views from the properties of the corresponding object in its items array. Objects in the items array need not all be of the same object type, but they must all decend from NSObject.

‘SCArrayOfItemsModel’ will automatically generate a set of SCArrayOfObjectsSection(s) if the sectionHeaderTitleForItem modelAction is implemented, otherwise it will only generate a single SCArrayOfObjectsSection.

This class functions as an SCTableViewModel section that is able to represent an array of any kind of objects and automatically generate its cells from these objects. In addition, ‘SCArrayOfObjectsSection’ generates its detail views from the properties of the corresponding object in its items array. Objects in the items array need not all be of the same object type, but they must all decend from NSObject. If more than one type of object is present in the items array, then their respective class definitions should be added to the itemsClassDefinitions set.

SCArrayStore is an SCDataStore subclass that encapsulates NSArray memory storage, providing means for the SC framework to communicate with this array storage to fetch, add, update and remove data objects.

This class provides as a badge view similar to the one used by iPhone’s mail application to display the number of messages in an inbox. SCBadgeView is typically used by SCTableViewCell to display these kind of badges.

Sample use: SCTableViewCell *cell = [SCTableViewCell cellWithText:@“Number of pending tasks”]; cell.badgeView.text = @“50”;

See also: SCTableViewCell

This class hosts a set of cell action blocks. Once an action is set to a desired code block, it will execute the block as soon as the action occurs.

This class functions as a means to further extend the definition of user-defined classes. Using class definitions, classes like SCObjectCell and SCObjectSection will be able to better generate user interface elements that truly represent the properties of their bound objects. For more information, please refer to SCDataDefinition.

Upon creation, SCClassDefinition will (optionally) automatically generate all the property definitions for the given class. From there, the user will be able to customize the generated property definitions, add new definitions, or remove generated definitions.

Sample use: // Extend the definition of ‘Task’ (user defined class) SCClassDefinition *taskDef = [SCClassDefinition definitionWithClass:[Task class] propertyNamesString:@“Task Details:(name,description,category,dueDate);Task Status:(completed)”]; SCPropertyDefinition *namePropertyDef = [taskDef propertyDefinitionWithName:@“name”]; namePropertyDef.required = TRUE; SCPropertyDefinition *descPropertyDef = [taskDef propertyDefinitionWithName:@“description”]; descPropertyDef.type = SCPropertyTypeTextView; SCPropertyDefinition *categoryPropertyDef = [taskDef propertyDefinitionWithName:@“category”]; categoryPropertyDef.type = SCPropertyTypeSelection; NSArray *categoryItems = [NSArray arrayWithObjects:@“Home”, @“Work”, @“Other”, nil]; categoryPropertyDef.attributes = [SCSelectionAttributes attributesWithItems:categoryItems allowMultipleSelection:NO allowNoSelection:NO];

SCCoreDataFetchOptions further extends the SCDataFetchOptions subclass to control how data is fetched from SCCoreDataStore.

SCCoreDataStore is an SCDataStore subclass that encapsulates Core Data persistent storage, providing means for the SC framework to communicate with this storage to fetch, add, update and remove data objects.

This class functions as a means to further extend the definition of user-defined data structures, such as classes and Core Data entities. This enables the framework to automatically generate user interfaces that accurately resemble these structures.

‘SCDataDefinition’ mainly consists of one or more property definitions of type SCPropertyDefinition. The property definitions can be placed in one or more property groups that will control how the properties are grouped when the user interface is generated. If no property groups are assigned, all property definitions are placed in a single defaultPropertyGroup.

See also: SCClassDefinition, SCDictionaryDefinition, SCEntityDefinition, SCWebServiceDefinition

This class is used to control how data is fetched from SCDataStore. SCDataFetchOptions can be configured to have the data sorted, filtered, and/or returned in batches.

Sample use: SCArrayOfObjectsModel *myObjectsModel = …; myObjectsModel.dataFetchOptions.sort = TRUE;

See also: SCDataStore, SCCoreDataFetchOptions, SCWebServiceFetchOptions

SCDataStore is an abstract base class that can encapsulate any kind of data storage, providing means for the SC framework to communicate with this storage to fetch, add, update and remove data.

Several SCDataStore subclasses have been implemented to enable the SC framework to communicate with Core Data, web services, iCloud storage, and even NSUserDefaults storage. Feel free to subclass SCDataStore to enable any kind of data storage not currently implemented by framework.

Sample use: // Display all the TaskEntity objects SCCoreDataStore *coreDataStore = [SCCoreDataStore storeWithManagedObjectContext:context defaultEntityDefinition:TaskEntityDef]; SCArrayOfObjectsSection *tasksSection = [SCArrayOfObjectsSection sectionWithHeaderTitle:@“Task Objects” dataStore:coreDataStore]; [self.tableViewModel addSection:tasksSection];

See also: SCArrayStore, SCCoreDataStore, SCWebServiceStore, SCiCloudStore, SCUserDefaultsStore

Undocumented

Undocumented

This class functions as a means to represent the definition of an NSDate class.

This class is typically used when you need to work with a collection of NSDate objects in classes like SCArrayOfObjectsSection and SCArrayOfObjectsModel. The class automatically generates only one property definition representing how the NSDate automatically generated UI should be defined.

This class is used to specify options for automatically generated detail view controllers.

Use this class to specify options such has how the automatically generated detail views are presented, their navigation bar type, their title, and/or their table view style.

Sample use: SCArrayOfObjectsModel *myObjectsModel = …; myObjectsModel.detailViewControllerOptions.presentationMode = SCPresentationModeModal;

This class functions as a means to further extend the key definitions of an NSMutableDictionary.

Using dictionary definitions, classes like SCObjectCell and SCObjectSection will be able to better generate user interface elements that truly represent the keys of their bound mutable dictionaries.

Sample use: // Define the dictionary using SCDictionaryDefinition SCDictionaryDefinition *dictionaryDef = [SCDictionaryDefinition definitionWithDictionaryKeyNamesString:@“key1;key2;key3”]; [dictionaryDef propertyDefinitionWithName:@“key2”].type = SCPropertyTypeSwitch; [dictionaryDef propertyDefinitionWithName:@“key3”].type = SCPropertyTypeSlider;

// Create some sample data NSMutableDictionary *dictionary = [NSMutableDictionary dictionary]; [dictionary setValue:@“Text” forKey:@“key1”]; [dictionary setValue:[NSNumber numberWithBool:YES] forKey:@“key2”]; [dictionary setValue:[NSNumber numberWithFloat:0.7f] forKey:@“key3”];

// Generate sections for the dictionary [self.tableViewModel generateSectionsForObject:dictionary withDefinition:dictionaryDef];

This class functions as a means to further extend the definition of user-defined Core Data entities. Using entity definitions, classes like SCObjectCell and SCObjectSection will be able to better generate user interface elements that truly represent the properties of their bound objects.

SCEntityDefinition mainly consists of one or more property definitions of type SCPropertyDefinition. Upon creation, SCEntityDefinition will (optionally) automatically generate all the property definitions for the given entity. From there, the user will be able to customize the generated property definitions, add new definitions, or remove generated definitions.

Sample use: // Extend the definition of ‘TaskEntity’ (user defined Core Data entity) SCEntityDefinition *taskDef = [SCEntityDefinition definitionWithEntityName:@“TaskEntity” managedObjectContext:context propertyNamesString:@“Task Details:(name,description,category,dueDate);Task Status:(completed)”]; SCPropertyDefinition *namePropertyDef = [taskDef propertyDefinitionWithName:@“name”]; namePropertyDef.required = TRUE; SCPropertyDefinition *descPropertyDef = [taskDef propertyDefinitionWithName:@“description”]; descPropertyDef.type = SCPropertyTypeTextView; SCPropertyDefinition *categoryPropertyDef = [taskDef propertyDefinitionWithName:@“category”]; categoryPropertyDef.type = SCPropertyTypeSelection; NSArray *categoryItems = [NSArray arrayWithObjects:@“Home”, @“Work”, @“Other”, nil]; categoryPropertyDef.attributes = [SCSelectionAttributes attributesWithItems:categoryItems allowMultipleSelection:NO allowNoSelection:NO];

SCExpandCollapseCell is a special cell class that, once tapped, collapses its owner section’s contents into a single cell. When tapped again, it will expand the section’s contents to their original state.

Sample use: mySection.expandCollapseCell = [SCExpandCollapseCell cellWithExpandText:@“Expand Section” collapseText:@“Collapse Section” ownerSectionExpanded:FALSE];

See also: SCTableViewSection

SCFetchItemsCell is a special cell that is automatically displayed by an SCArrayOfItemsSection when more section items need to be fetched. This is typically the case when the section’s dataFetchOptions property has specified a batchSize for the fetched items.

Sample use: myArrayOfObjectsSection.dataFetchOptions.batchSize = 10; myArrayOfObjectsSection.fetchItemsCell.textLabel.text = @“Load next batch”;

See also: SCArrayOfItemsSection

This class defines a set of internal helper methods

This class defines a tabel view model center.

This special view provides an accessory view that automatically appears on top of the keyboard, providing navigation functionality between the different text controls. The view provides ‘Next’, ‘Previous’, and ‘Done’ buttons. It also provides a special ‘Clear’ button for cells such as SCDateCell.

Sample use: self.tableViewModel.inputAccessoryView.rewind = FALSE;

See also: SCTableViewModel

This class hosts a set of model action blocks. Once an action is set to a desired code block, it will execute the block as soon as the action occurs.

This class functions as a means to represent the definition of an NSNumber class.

This class is typically used when you need to work with a collection of NSNumber objects in classes like SCArrayOfObjectsSection and SCArrayOfObjectsModel. The class automatically generates only one property definition representing how the NSNumber automatically generated UI should be defined.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeObjectSelection, thus allowing further customization of the generated control by the user.

Undocumented

This class is an abstract base class that represents a set of SCPropertyDefinition attributes.

Each subclass of ‘SCPropertyAttributes’ is used to extend the definition of an SCPropertyDefinition instance according to its respective type. Set the attributes property of an SCPropertyDefinition instance to a subclass to be able to further customize the user interface element that will be generated for this property definition.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeTextView, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeTextField, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeNumericTextField, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeSlider, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeSegmented, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeDate, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeSelection, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeObject, thus allowing further customization of the generated control by the user.

This class is used to extend the definition of an ‘SCPropertyAttributes’ instance of type SCPropertyTypeArrayOfObjects, thus allowing further customization of the generated control by the user.

This class functions as a property definition for SCDataDefinition.

Every property definition should set a property type that determines which user interface element should be generated for the property. In addition, the generated user interface element can be further customized using the property’s attributes.

This class functions as a property definition for SCDataDefinition that will generate a custom user inteface element (e.g.: custom cell).

‘SCCustomPropertyDefinition’ does not have to represent a property that actually exists in its class (unlike an SCPropertyDefiniton), and is often used in a structure definition as a placeholder for custom user interface element generation.

This class functions as a way to define a property definition group that is used to generate a corresponding user interface element that groups these properties (e.g.: a table view section).

Property definitions are added to this class using their NSString ‘name’ property.

This class functions as an array of SCPropertyGroup objects.

This special view provides table views with the common pull-to-refresh functionality.

Once pull-to-refresh is enabled in the table view model, this view will automatically handle displaying the pull messsage, inform the model that the table view needs refreshing, and return back to normal state after the table view has done refreshing its contents.

Sample use: self.tableViewModel.enablePullToRefresh = TRUE; self.tableViewModel.pullToRefreshView.pullStateText = @“Pull to refresh tasks”; self.tableViewModel.pullToRefreshView.releaseStateText = @“Release to refresh tasks”; self.tableViewModel.pullToRefreshView.loadingStateText = @“Loading new tasks…”;

See also: SCTableViewModel

This class functions as a means to simplify creating view controllers dedicated to searching data within a table view.

In addition to all the features provided by its SCViewController superclass, SCSeachViewController conveniently provides a UISearchBar control and a UITableView control aligned under each other. In addition, SCSearchViewController defaults to automatically displaying a UISearchDisplayController when a search is performed.

This class hosts a set of section action blocks. Once an action is set to a desired code block, it will execute the block as soon as the action occurs.

This class functions as a means to represent the definition of an NSString class.

This class is typically used when you need to work with a collection of NSString objects in classes like SCArrayOfObjectsSection and SCArrayOfObjectsModel. The class automatically generates only one property definition representing how the NSString automatically generated UI should be defined.

This class functions as a cell for SCTableViewSection. SCTableViewCell is extensively subclassed to create cells with special controls such as UITextField and UISlider.

SCTableViewCell provides the user with the infrastructure to access the cell’s value using the Bound Object method. This works by binding the cell to an object, called the bound object, and to a property of this object, called the bound property. The cell initializes its value from the value of the bound property, and when its values changes, it sets the property back automatically.

Please note that even though a cell value is not applicable to SCTableViewCell itself, SCTableViewCell still provides the bound object functionality as a framework to all its subclasses to use.

This class functions as a base class for all user defined custom cells.

The following is a summary of each control that can be automatically bound, in addition to the corresponding boundObject property value type that it must be associated with:

• UILabel: NSString, NSNumber, NSDate
• UITextField: NSString, NSNumber, NSDate
• UITextView: NSString, NSNumber, NSDate
• UISlider: NSNumber, NSString
• UISegmentedControl: NSNumber, NSString
• UISwitch: NSNumber
• UIImage: NSString

This class functions as a base class for all cells that require user controls to be present inside their content view.

This class functions as a cell with a UILabel control. The bound property of this cell can be of any type the decends from NSObject.

This class functions as a cell with a UITextView control. The bound property of this cell must be of type NSString.

This class functions as a cell with a UITextField control. The bound property of this cell must be of type NSString.

This class functions as a cell with a UITextField control with numeric values. The bound property of this cell must be of type NSNumber, int, float, or double. SCNumericTextFieldCell defines its own validation rules according to the following criteria:

• Value is valid only if it’s a numeric value.
• If minimumValue is not nil, then value is only valid if it’s greater than or equal to this value.
• If maximumValue is not nil, then value is only valid if it’s less than or equal to this value.
• If allowFloatValue is FALSE, then value is only valid if it’s an integer value.

This class functions as a cell with a UISlider control. The bound property of this cell must be of type NSNumber, int, float, or double.

This class functions as a cell with a UISegmentedControl. The bound property of this cell must be of type NSNumber, int, or NSString.

This class functions as a cell with a UISwitch control. The bound property of this cell must be of type NSNumber or BOOL.

This class functions as a cell that provides the end-user with a UIDatePicker to choose a date with. The bound property of this cell must be of type NSDate.

This class functions as a cell that provides the end-user with an automatically generated detail view of type UIImagePickerController to pick an image with. As soon as the image is picked, it will be saved to the Documents folder using either an auto generated name from the current time stamp, or a name provided through SCTableViewModelDelegate or the cell’s actions. The bound property of this cell must be of type NSString, and will be bound to the name of the selected image. Once an image is selected, tapping an SCImagePickerCell will display the image in a detail view. To select a different image, the table view must be put in edit mode (make sure UITableView’s allowsSelectionDuringEditing property is TRUE). Alternatively, make sure that displayClearImageButtonInDetailView property is TRUE, and the user will be able to tap a “Clear Image” button to clear the selected image.

This class functions as a cell that provides the end-user with an automatically generated detail view of options to choose from, much like the Ringtone selection cell in the iPhone’s sound settings. The selection items are provided in the form of an array of NSStrings, called the items array. ‘SCSelectionCell’ can be configured to allow multiple selection and to allow no selection at all. the bound property of this cell must be of type NSNumber, NSString, or NSMutableSet. If allowMultipleSelection is TRUE, then only NSString and NSMutableSet property types are allowed.

This class functions as a cell that provides the end-user with an automatically generated detail view of objects to choose from.

The selection items are provided in the form of an array of NSObjects, called the items array. ‘SCObjectSelectionCell’ can be configured to allow multiple selection and to allow no selection at all. If allow multiple selection is disabled, then the bound property name of this cell must be of type NSObject, otherwise it must be of type NSMutableSet.

This class functions as a cell that is able to automatically generate a detail view with cells generated from a given bound object’s properties.

If the bound object is given without an extended class definition (SCClassDefinition), then the cells will only be generated for properties of type NSString and NSNumber, and will be either of type SCTextFieldCell or SCNumericTextFieldCell, respectively. If an SCClassDefinition is provided for the bound object, a full fledged detail view of cells will be generated.

When SCObjectCell is selected by the end-user, a detail view optionally fires up to to give the user the ability to edit the object’s properties.

This class functions as a means to simplify development with SCTableViewModel.

SCTableViewController conveniently provides several ready made navigation bar types based on SCNavigationBarType, provided that it is a subview of a navigation controller. SCTableViewController also defines placeholders for a tableView and a tableViewModel that the user can allocate and assign. If a tableViewModel is defined, SCTableViewController also connects its doneButton (if present) to tableViewModel’s commitButton automatically.

In addition, SCTableViewController fully manages memory warnings and makes sure the assigned table view is released once a memory warning occurs and reloaded once the view controller is loaded once more.

Finally, SCTableViewController provides several useful actions (SCTableViewControllerActions) that notify the delegate object of events like the view appearing or disappearing.

This class hosts a set of view controller action blocks. Once an action is set to a desired code block, it will execute the block as soon as the action occurs.

SCTableViewControllerAction_Block syntax: action = ^(SCTableViewController *viewController) { // Your code here };

This class is the master mind behind all of Sensible TableView’s functionality.

Sensible TableView provides an alternative easy way to create sophisticated table views very quickly. The sophistication of these table views can range from simple text cells, to cells with controls, to custom cells that get automatically generated from your own classes. SCTableViewModel also automatically generates detail views for common tasks such as selecting cell values or creating new objects. Using SCTableViewModel, you can easily create full functioning applications in a matter of minutes.

SCTableViewModel is designed to be loosely coupled with your user interface elements. What this means is that you can use SCTableViewModel with Apple’s default UITableView or with any of your custom UITableView subclasses. Similarly, you can use SCTableViewModel with any UIViewController, or any of its subclasses, including UITableViewController or your own subclasses.

Architecture:

An SCTableViewModel defines a table view model with several sections, each section being of type SCTableViewSection. Each SCTableViewSection can contain several cells, each cell being of type SCTableViewCell.

This class subclasses SCTableViewModel to represent an array of any kind of items and will automatically generate its cells from these items. ‘SCArrayOfItemsModel will automatically generate a set of SCArrayOfItemsSection(s) if the sectionHeaderTitleForItem modelAction is implemented, otherwise it will only generate a single SCArrayOfItemsSection.

This class functions as a table view model that is able to represent an array of string items and automatically generate its cells from these items. The class inherits all its funtionality from its superclass: SCArrayOfItemsModel, except that its items array can only contain items of type NSString. ‘SCArrayOfStringsModel will automatically generate a set of SCArrayOfStringsSection(s) if the sectionHeaderTitleForItem modelAction is implemented, otherwise it will only generate a single SCArrayOfStringsSection.

This class functions as a model that is able to provide selection functionality. The cells in this model represent different items that the end-user can select from, and they are generated from NSStrings in its items array. Once a cell is selected, a checkmark appears next to it, similar to Apple’s Settings application where a user selects a Ringtone for their iPhone. The section can be configured to allow multiple selection and to allow no selection at all.

Since this model is based on SCArrayOfStringsModel, it supports automatically generated sections and automatic search functionality.

There are three ways to set/retrieve the section’s selection:

• Through binding an object to the model, and specifying a property name to bind the selection index result to. The bound property must be of type NSMutableSet if multiple selection is allowed, otherwise it must be of type NSNumber or NSString.

• Through the selectedItemsIndexes or selectedItemIndex properties.

This class functions as a model that provides the end-user with an automatically generated list of objects to choose from.

The selection items are provided in the form of an array of NSObjects, called the items array. ‘SCObjectSelectionModel’ can be configured to allow multiple selection and to allow no selection at all. If allow multiple selection is disabled, then the bound property name of this model must be of type NSObject, otherwise it must be of type NSMutableSet.

This class functions as a section for SCTableViewModel. Every ‘SCTableViewSection’ can contain any number of SCTableViewCell(s).

This class functions as an SCTableViewModel section that is able to automatically generate its cells from a given bound object’s properties. If the bound object is given without an extended class definition (SCClassDefinition), then cells will only be generated for properties of type NSString and NSNumber, and will be either of type SCTextFieldCell or SCNumericTextFieldCell, respectively. If an SCClassDefinition is provided for the bound object, a full fledged section of cells will be generated.

@note: For your convenience, the tag property of each generated cell will have a number corresponding to the index of it’s corresponding property in bound object.

This class functions as an SCTableViewModel section that is able to represent an array of any kind of items and automatically generate its cells from these items. The section is also able to handle all end-user interaction with the generated cells, including adding, editing, deleting, and moving the cells. When cells are added or edited, detail views are automatically generated for this purpose. To enable adding cells, the class’ user should set the addButtonItem property of the section to a valid UIBarButtonItem, the section then will automatically add new items when the button is tapped.

When adding new items to the array, the section starts by first asking the model’s data source to provide a new item using its tableViewModel:newItemForArrayOfItemsSectionAtIndex: SCTableViewModelDataSource protocol method.

This class is an abstract base class. Subclasses of this class must override the buildDetailTableModel method. This method should return a model for the detail view to display.

This class functions as an SCTableViewModel section that is able to represent an array of string items and automatically generate its cells from these items. The class inherits all its funtionality from its superclass: SCArrayOfItemsSection, except that its items array can only contain items of type NSString.

This class functions as an SCTableViewModel section that is able to provide selection functionality. The cells in this section represent different items that the end-user can select from, and they are generated from NSStrings in its items array. Once a cell is selected, a checkmark appears next to it, similar to Apple’s Settings application where a user selects a Ringtone for their iPhone. The section can be configured to allow multiple selection and to allow no selection at all.

There are three ways to set/retrieve the section’s selection:

• Through binding an object to the section, and specifying a property name to bind the selection index result to. The bound property must be of type NSMutableSet if multiple selection is allowed, otherwise it must be of type NSNumber or NSString.
• Through binding a key to the section and setting/retrieving through the ownerTableViewModel modelKeyValues property.

• Through the selectedItemsIndexes or selectedItemIndex properties.

This class functions as a section that provides the end-user with an automatically generated list objects to choose from.

The selection items are provided in the form of an array of NSObjects, called the items array. ‘SCObjectSelectionSection’ can be configured to allow multiple selection and to allow no selection at all. If allow multiple selection is disabled, then the bound property name of this section must be of type NSObject, otherwise it must be of type NSMutableSet.

The SCTheme class enables CSS-like styling of UIView (or any of its subclasses). Using CSS-like text files, any UIView property with a supported data type can be set. Key-path property format is fully supported (e.g. layer.cornerRadius: 5). All pointer data types accept nil as value (e.g. backgroundView: nil;).

Supported property data types:

Data Type -> Format in .sct file

NSString* -> A string between single or double quotes. Example: detailTextLabel.text: “Hello World!”;

CGFloat -> A normal number. Example: height: 60;

BOOL -> Possible values: TRUE, FALSE, YES, NO. All case insensitive. Example: clipsToBounds: NO;

UIColor* -> Any UIColor color name constructor. Example: backgroundColor: blueColor; or rgb(redValue, greenValue, blueValue, optionalAlphaValue) Example: backgroundColor: rgb(100, 0, 255); or #hexValue Example: backgroundColor: #CC33FF or A string containing an image resource. Example: backgroundColor: “background.png”;

CGColorRef -> Format identical to UIColor. Example: layer.borderColor: redColor;

CGRect -> CGRect(x, y, width, height) Example: textLabel.frame: CGRect(10, 10, 180, 30);

CGSize -> CGSize(width, height) Example: textLabel.shadowColor: darkGrayColor; textLabel.shadowOffset: CGSize(1, 1);

UIImage* -> A string containing the image resource. Example: backgroundImage: “background.png” or A string containing the image resource and capInsets(top, left, bottom, right). Example: backgroundImage: “background.png” capInsets(0,0,0,0)

UIFont* -> Font name and size separated by a space. A good resource for font names is: http://iosfonts.com/ Example: textLabel.font: Courier-Bold 12;

UIView* -> A string containing an image resource that will be loaded into a UIImageView. Example: backgroundView: “background.png”;

UITableViewCellSeparatorStyle Any valid UITableViewCellSeparatorStyle constant. Example: separatorStyle: UITableViewCellSeparatorStyleNone;

Sample theme file: MyTheme.sct UINavigationBar { backgroundImage: “navbar-background.png”; }

UITableView { backgroundView: “leather-background.png”; }

SCTableViewSection { firstCellThemeStyle: firstCell; oddCellsThemeStyle: oddCell; evenCellsThemeStyle: evenCell; lastCellThemeStyle: lastCell; }

firstCell { backgroundView: “firstCell-background.png”; selectedBackgroundView: “selectedFirstCell-background.png”; }

oddCell { backgroundView: “oddCell-background.png”; selectedBackgroundView: “selectedOddCell-background.png”; }

evenCell { backgroundView: “evenCell-background.png”; selectedBackgroundView: “selectedEvenCell-background.png”; }

lastCell { backgroundView: “lastCell-background.png”; selectedBackgroundView: “selectedLastCell-background.png”; }

Sample code needed to use the above theme file: self.tableViewModel.theme = [SCTheme themeWithPath:@“MyTheme.sct”];

This class functions as a means to define NSUserDefaults fields that the framework can automatically generate a user interface for. As with all other types of binding, once the UI is generated, the framework will also be responsible for automatically reading and writing the values to NSUserDefaults.

Sample use: // Create the user defaults definition SCUserDefaultsDefinition *userDefaultsDef = [SCUserDefaultsDefinition definitionWithUserDefaultsKeyNamesString: @“Login Details:(username,password):Will be automatically signed in”]; SCPropertyDefinition *passwordDef = [userDefaultsDef propertyDefinitionWithName:@“password”]; passwordDef.attributes = [SCTextFieldAttributes attributesWithPlaceholder:nil secureTextEntry:YES autocorrectionType:UITextAutocorrectionTypeNo autocapitalizationType:UITextAutocapitalizationTypeNone];

// Generate the UI for the user defaults [self.tableViewModel generateSectionsForUserDefaultsDefinition:userDefaultsDef];

SCUserDefaultsStore is an SCDataStore subclass that encapsulates the NSUserDefaults storage, providing means for the SC framework to communicate with this storage to fetch, add, update and remove user defaults.

This class functions as a means to simplify development with SCTableViewModel.

SCViewController conveniently provides several ready made navigation bar types based on SCNavigationBarType, provided that it is a subview of a navigation controller. ‘SCViewController’ also defines placeholders for a tableView and a tableViewModel that the user can allocate and assign. If a tableViewModel is defined, SCViewController also connects its doneButton (if present) to tableViewModel’s commitButton automatically.

In addition, SCViewController fully manages memory warnings and makes sure the assigned table view is released once a memory warning occurs and reloaded once the view controller is loaded once more.

Finally, SCViewController provides several useful actions (SCViewControllerActions) and delegate methods (SCViewControllerDelegate) that notify the delegate object of events like the view appearing or disappearing.

This class hosts a set of view controller action blocks. Once an action is set to a desired code block, it will execute the block as soon as the action occurs.

SCViewControllerAction_Block syntax: action = ^(SCViewController *viewController) { // Your code here };