I am developing a web page. This page contains a list of items on the left side, and a information panel on the right side to show some summary information specific to the selected items see below:
When one item is selected by user, the information panel's content should be updated to show the active item's content.
My Question:
What is the proper way to implement this:
Spawn one information panel per list item. Then hide/show the the information panel for the active list item.
Make only one information panel globally. Then update the information panel's content based on list item selection?
Because I am using Angular 2 and Bootstrap, advices specific to these libraries are appreciated. (For example, shall I use route to implement the item-click-to-summary-display? Is there a component in Bootstrap library that is specifically for such purposes? )
Related
I'm trying to create tabbed list view where I have a filtered list of users in every tab. The problem is that the pagination on the bottom is one for all tabs it doesn't change. When I use it it tries to change the page of all tabs.
What I did is to put List in every Tab and I have a Datagrid in the List.
Is there anything I can do for the pagination?
This won't work unless you rewrite the List component completely.
I suggest you to have a custom menu instead, with an entry for each of your current tabs and defining the filters in the menu item urls.
I have successfully implemented the FuelUx tree control but I want the user to click a different status check mark (IE active or archived) and only display the child items in the tree that contain the selected status.
Any suggestions on how to implement this feature?
Thanks,
Greg
My first inclination would be to add an active/inactive/archived/whatever class to the data source attr.cssClass key.
http://getfuelux.com/javascript.html#tree-usage-datasource
This would allow you to toggle which item state is being displayed at a given time. You could also use styles connected to the class to customize the icon based on the state.
I am making application for IPAD and I need to show split view there.
What is my requirement in this:
I will show a list in left panel (Data will not be for nested. I have only 1 level)
When I click on any item of list, it will load a another list in right panel.
In right panel , if I click on any item, it will show the detail page in the same view.
Can any one give me a working example for it?
I have ascenario like I have to place each of panel bar items into a seperate ajas.beginform. All the panel bar items were came through model binding.How can I solve this issue???
Regards
Mahesh
Yo
It seems you need to add form separately for each of your panelbar items - because if you surround the whole PanelBar - all the inputs from the other (even hidden/closed) items will be validated/submitted along with the inputs in the current opened item.
This is sort of a subjective question, but I'd like to get some ideas on the best way to lay this out. I'll set up the situation for you.
I have a grid with a column that allows the user to "View Details" on a particular item. The grid also allows the user to select multiple rows and "View Details" on those items. When the user clicks "View Details", a Window will pop over the grid, with a form inside it and controls to navigate between the multiple items (if they selected multiple items).
Here's a picture for an example:
I have no problem creating the Window, but I'm curious as to how to handle multiple "FormPanels", if that makes sense? Would I need to create another Panel inside the container Panel for each item they have selected, and then hide/show based on the active item (shown as "Item #1" in the dropdown)?
I'm thinking of it like a deck of cards in which you can navigate through, but I've never done something like this before. Also note that each item/card will be prepopulated with information from the grid, but that should be easy enough to do if I'm using the same Store.
Thoughts?
Yes you're right, and the layout you're looking for is the CardLayout.
You can read about it in the API here. The basic idea is like you said, a stack of cards that contain components, and you shuffle through them by calling the relevant methods.