i have a category navigation page in the category page which uses category navigation model .I want the category navigation page in the product page which uses product model and also i cant use category navigation model and product model in the same page.please suggest me some solution.
Related
I don’t have any code for this, so I’ll make up a hypothetical situation:
I want to make a grocery list app. I have a tab bar that sends me to a view where I can create categories in a list (fruits, vegetables, dairy etc.) Each category sends the user to a detail view where they can list off certain brands and the amount they need.
(This is where it gets a bit tricky)
In the main view, the categories that the user made are now tabs that are on the bottom and the list they made in detail view appears on the screen. Any changes they make in the list shown (in the main view) will update back into the specific detail view.
Is that possible? And what technique would be used for something like this?
In the top of my detailcontroller I have a button to show a list of selected items from various options on the detail controller.
I want to initialize and keep the model, the popover and the list objects in the mastercontroller. How can I get a reference to my mastercontroller to reuse these objects?
Sharing data between views is easiest using a model tied to the component. If you make sure that everything that's selected in the master model is contained in that model, you will be able to use the data from the model in the detail view again.
Pulling data directly from another controller would go against the MVC paradigm and is not recommended (although not impossible, using e.g. the sap.ui.getCore().byId() method). I would not go there unless you have a clear view of the consequences.
I have an application that uses MEF and Caliburn.Micro. The main view has canvas and a button. The button when clicked, should create a new widget and display it in the canvas. The widget in this case is a UserControl that has a view and viewmodel.
The user can add 0-N of these widgets to the canvas.
I have the widget in the MEF catalog but I can't seem to find an example of how to wire it up in Caliburn.Micro.
Any ideas what I'd write in the main view model when that button is pressed?
You should have a collection of view models that your Canvas binds to. In fact, if you use a Conductor collection type in Caliburn.Micro (have a look at Conductor<T>.Collection.AllActive), then it already has an Items collection.
When the button is clicked, your main view model verb (method) can add a new view model to the Items collection. Your main view model will therefore need a view model factory injected in order to create these child view models.
I am developing an iphone app for a class project and am displaying a bunch of different products. I am trying to create a favorites page where users can add one of the products to their favorites page. The app is set up with a bunch of different tableviews to display the different products along with their piture, name, price, and description. I want the user to either click on my addtofavorites button I will add to each of the table view cells or I was wandering if I can just use the didSelectRowAtIndexPath method in the tableviews to add all that information to the favorites table view. Thank you
First, look into following the MVC pattern,
a good introduction: https://developer.apple.com/library/mac/#documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html
That being said, I'd have a products UITableView, in a view controller. The user can then select the view controller and in the didSelectRow: method, find out which product was selected to sou can pass the data through a delegate patterns (other ways include target-action, NSNotification, etc.) for example like this: (good example of passing data: Passing Data between View Controllers) to a separate view controller which would hold your favorites table view. Make sure the model is separate from both the products view controller and favorites view controller so you can save all the name, price, etc whatever properties you want to save.
perhaps all of this would be contained in a UITabBarController so it's easier for the user to go back and forth between products and favorites.
I have a data-driven table view. The root view displays a list of entities (1) that when selected displays another list of entities (2).
If an entity in (1) has a series of properties that I'd like the user to have control over, what's the best UI approach to presenting them with a window for editing this data?
For example, if (1) was a list of Continents and (2) was a list of Countries, tapping a Continent will present a list of Countries and so on. If The user wanted to change a property of a Continent (example change "rateThisContinent") what does convention say he/she should tap?
I was originally thinking of a detail disclosure but that's not really in line with Apple's guidelines for what detail disclosure is.
An edit button might be the way to go, but then what would the table view display after the edit button has been pressed?
Thanks,
Glyn
I've decided to answer my own question. I will create an intermediate 'detail view' after the (1) list that presents all the properties with a button to view the (2) list.
I'll then make the detail view editable.