two (2) table view on one (1) view controller - xcode

is it possible to have 2 table view controllers in 1 view controller? And can you help with this?
I'm making a simple app that requires 2 tableview to present the client database and the "Activity" of a selected client. so, 2 table view will be needed to populate the client list and the Activity Lists.
This application will be used on an iPad.

Related

How to cross update of view between nattable and Jface view

Eclipse RCP View Communication ,where one view contains nattable and another views contains jface controls like button, dropdown.
Currently for example there is 3 view/Editor as shown below
View1 - contains employee details which is a Nattable and
it's cell contains data like String, Long, boolean, date value.
each row represent one data,and other views are corresponding data of
selected row
View2 - shows Address which is corresponding to the selected row in the View 1,
User can modify data of view2.
View3 - shows department details of employe, which can also be modified
So all 3 views present data of one model say Employee
Employee
|_Name
|_EmpId
|_Married
|_DOJ
|_Address
|_Type
|_City Name
|_State
|_PinCode
|_Department Details
|_Department
|_Project
|_Manager
Problem:
I want to know what is best way of communcation between views1 and other view such that
On selection of row in view1 then other two view should be update correspondingly;
If any data changes in view2/view3 then view 1 should get notification for data change in other view
when condition 2 occurs then I want to show dirty row in view1.
The typical approach for inter view communication in an E4 application related to your described scenario is to use the ESelectionService to trigger handling of a selection for opening another view, and to communicate back via the Eclipse 4 event system.
For scenario one to open a view based on the selection in a NatTable you could use the E4SelectionListener in the NatTable Eclipse 4 Extension Feature. It is a ILayerListener that forwards the selection to the ESelectionService. An example can be found in the NatTable examples.
To inform view 1 about changes in another view, I would suggest to use the IEventBroker to send an event from view2/view3 and react on the event in view1. This way the views are decoupled as much as possible. Eclipse 4 event system is a good starting point for learning about the event system.

How to create a page that leads to multiple scrollviews in swift

The beginning page is a table view. On the table view there is table that contains four different topics(picture provided). I would like each topic to lead to a new page that is a scroll view. I have successfully programmed so that the first topic will lead to a scroll view. However, I am having trouble creating more than one scroll view page for each topic. enter image description here
How to:
Create destination view controllers in your storyboard.
Create segues by CTRL-dragging from cell to the view controller that should be shown when the cell is tapped.

Connect two NSObjectControllers within a multi view OSX Storyboard

I'm using Storyboards for the first time creating a master/detail view for a simple object.
Both view controller items of the split view have their own view & NSObjectControllers. The controller for the table view is a NSArrayController (which shows all instances of the Entity). The controller for the detail view is an NSObjectController, which shows just the selected instance.
When I click an object in the table, I'd like the detail to show up in the detail view. So I believe my goal here is to bind the 'contents' of the detail object controller to the 'selection' of the master array controller. However with storyboards I cannot cross view controller boundaries (can't create the IB 'link'. aka: can't bind cross VC).
Whats the best practice for doing this?
So far all I can think to do is manually set all this up in one of the controllers (either the root controller, window controller or perhaps the master table view controller) - but that seems counterintuitive. That seems to defeat the purpose of being able to lay out this stuff within storyboards in the first place, and my controller of choice would then have to know about the other controller specifically.
I must be missing something!

iOS: How to update/reload tableview when swip pages in container view

I have a question on my app,
The main view (mainviewcontroller.h)consists of 2 views, 1 container view and 1 tableview, inside the container view it's a pageviewcontroller (pageviewcontroller.h) which controls 5 pages, 5 pages share same viewcontroller(uiviewcontroller.h)
Question is when I swip through the pages, I want the tableview reload data according to the page.
The data in table view is coming from a preloaded database. I can get different table of data by changing predicates keywords in the fetch request, but how can I somehow link the changing of page in the pageviewcontroller to change of predicate in the fetch request.
Any input is appreciated.

Mutually exclusive search options on MVC 3 view

I'm working up a view that will use 2 sets of search options and would like to know if there is better way than I'm headed.
on right hand side it will search by username, lastname
on left hand side it will search by an entity type or entity name
the results should be returned as a grid below the search.
I've considered that I may need 2 forms on the view but not sure if that is the right direction. Would 2 partial views each with their own form be better? If so, how would data be returned to the main view?
I'm trying to keep this simple by posting to controller actions and returning views instead of a bunch of confusing jquery.
Currently I have a model with 2 sub-models that each define the search fields that will allow a user to enter data into the textboxes.
What is the proper way to handle this in MVC 3?
You can use two partial views if you are going to re-use the forms on other views or if you just want to encapsulate the view code. I would suggest two forms that post to different controller actions 'SearchPerson(model), SearchEntity(model). Both actions can return a common 'Results' view model to a 'SearchResults' view.

Resources