Great...
Here are the main guidelines that you should be following:
1. Storage:
a. If both views have an identical set of data (and you don't envision that this will ever change in the future), then create just one Core Data entity that will store the field values of both views. In this case, you'll be creating two Core Data objects as soon as the application starts for the first time, one object for each view.
b. If each view has a separate set of data, then create an entity for each view (I personally prefer this option). As soon as the application is launched for the first time, create an object from each of the two entities.
2. UI (in each one of the view controllers):
a. Create the class definition normally for the respective entity.
b. Create an SCObjectSection with this class definition, and associate it with the object that was created earlier (see "Storage" above). Here is a code sample:
...
SCObjectSection *objectSection =
[SCObjectSection sectionWithHeaderTitle:nil
withBoundObject:sideAObject withClassDefinition:sideAClassDef];
[tableModel addSection:objectSection];
...
c. Detect any modifications that happen inside each view and do whatever you need to update the other view's object's fields. You can detect modifications by implementing the SCTableViewModelDelegate method called "tableViewModel:valueChangedForRowAtIndexPath:"
Hope this helps!
