I am working on a table drill-down style iPhone app that has created the data I can populate the views of the table For Core Data and the NSFATed Resolutions Controller, which shows the object (managed object) in the final level of the table view, I want my user to be able to select the item which will eventually show up in another view. Interpretation is. This second view will be like a favorite list (implemented in a tabbed view). The user will have an option to delete or add other items to Favorites.
My model has three entities, which represent a level of each table view. The high level institution has many relationships along with the low level institution, and the inverse relationship is one
How to use the current managed object (the object in the last level of the table view) to save it Do and show this favorite list is in the scene? Should I make a new unit and establish a relationship between the two?
My model has three entities, each representing table view table.
He is thinking backwards that you have three bodies that are logically present in a hierarchy and the hierarchy of the scenes shows that logical structure. There are ideas to display the data, the data does not exist for displaying the scene. This is an important concept to understand and if you fail to do so, then your app design will always be more complex, fragile, and difficult to maintain and maintain. Data models always come first and the logical relationship within the data model And the user interacts with that data eventually applying the UI structure of the app.
This is a simple trap because the instruction material always starts with the interface first time. However, in real app design, you start with the first data model and work further for the interface.
In this case, if you want to store some of the favorites of the unit, then you have two options, if an institution is preferred, then the core relationship between the data and the user is part of the relationship and you only have to If you have a set, you can legitimately add the "isFavorite" attribute to a boolean unit and then you can get to those organizations where "isFavorite == yes"; If you have a list of favorites, then the most preferred method will be to create a favorite list and then each favorite unit should relate to those items about which this list is about.
If the user has intermediate and peripheral interaction with the preferred data, you can store the object ID in the user default.
Comments
Post a Comment