Best component to show three columns - dictionary

I am struggling myself thinking about which component to use in my new app.
The first screen I am using Collection View with big images. Once the user touches one cell, it goes to the second screen ... and here is the problem.
I have three columns, similar to a dictionary with first language, second and third. The user will be able to choose which column he wants to search, and according to his criteria it will show the result that matches. I am not sure how to implement this, which component gives the best experience to the user. Any idea is more than welcome. Thank you in advance. Alex

If your data is several rows each with 3 columns, I would recommend customizing a UITableView. I followed this tutorial when I was trying to set up something similar.
The Table View will also give you efficiency if you have a lot of data, and you can build the custom table cells in the interface builder so that makes life a little easier.
-Ken

Related

multiple actions on button with if statement in xcode4

First of all, I'm very new to the Xcode 4 and Obj C and I m trying to build a survey function with only one navigation button. I need a method for my navigation button which will produce the result that if users select the first option and then select the navigation button, it will bring them to the second view controller while if they select the second option the navigation button will take them to another view. Can someone please help
I am in the same boat. I wish that other people would have posted to this. If it helps at all, the if/else statement in the code snippet library probably holds the keys, now we just need to find the lock.
if (<#condition#>) {
<#statements-if-true#>
} else {
<#statements-if-false#>
}
I am still learning here, but I know that an important conceptual distinction is that you can handle this survey in one of at least two ways:
Use if/then logic to branch out to different questions.
Have the same questions for everyone, storing the answers in a plist file and then at the end, based on the results gather, branch at that point to final results screens.
This was posted last year so you may be well ahead of me, but as I find out more, I'll post here. I'll be happy to add to the reference resources.
– David

Variable number of categories/checkboxes

I am building a form for parents to enter health information for their students. Our nurses want to build it similar to what you fill out when you see a new doctor where they have categories and then conditions within the category that you would check if they apply to you. They want the number of categories and conditions to be variable so they can change them willy nilly as desired.
I need some ideas as to how to approach the UI side. My initial thought is a parent gridview with a row for each category and then inside that, a child gridview for each condition with its own checkbox. I already do a bit of work with gridviews and know how to access the nested objects so I'm not terribly worried about how to get the data back.
My question is this: Is there a better way and what suggestions would the community make that might be different or more efficient than using nested gridviews?
+1 for asking is there a better way?
What I'm about to suggest may end up being a little more complicated at first, but rest assured it will be worth it in the end.
There is a JavaScript framework named Knockout.js that is perfect for situations like these. Knockout vastly simplifies situations that where a variable amount of UI controls are needed.
http://knockoutjs.com/
Here is a tutorial on the website that has a similar situation to yours:
http://learn.knockoutjs.com/#/?tutorial=collections

Is it possible to create a table with a multi-level row using ASP.NET GridView or other control

I'm not sure if I'm using the correct terminology to describe my questions so I created a few mock ups to try to show what I am trying to do.
I have an existing table listing order detail information that looks something like this:
I have some additional attributes I want to add columns for, but I would like it to appear on a separate line as part of the same row sort of like this:
The reason I want to add these columns but have them appear on the second line of each row is that I want to display more data in each row but I don't want to make the row/page wider.
I did some googling for this problem, but I'm not even sure what the standard name for this type of display is so I wasn't able to come up with anything. The closest I found was [this code project link](http://www.codeproject.com/KB/webforms/MasterDetail.aspx
) which is close to, but not the same thing I am trying to do.
Not sure what to call it either (multiline gridview?) but it should be possible. I would suggest looking at making a grid with a template column and a formview inside the template. In the rowdatabound event of the grid you write code to bind your form to the row's data. I have used this technique before on nested grids, it should work with other controls as well. Might be simpler ways to do it too, not something I have had a need to work out before.
EDIT:
I just saw a similar question where someone provided a link to this article. Not quite what we were talking about here, but very similar. Thought I would include it here as well for future reference. To bad it was written 5 months after this question was asked...

AdvancedDataGrid SummryRow

One update:
I tried using the SummaryRow on the datagrid for its basic functionalities and it is working. Now, I need to embed the text in the summary fields. E.g. If one of my summaryfields returns me the count then it should be able to display 'TOTAL (count)'
Is it possible with the summaryrow?
Also, I need to have the data to be formatted when it is displayed. e.g. %age, like 50%, 0.1%, etc.
Is this also possible?
Hi,
One quick question. I have an AdvancedDataGrid. I need to add a summaryrow to the grid which will contain SUM/AVERAGE of the respective columns in the ADG. Can anyone point me to some tutorial or any reference where I can learn how to create a summaryrow?
Thanks!
The advancedDataGrids introduction from adobe contained a demo, but it doesn't seem to be on the web anymore. Have you tried looking at the SummaryField reference? I haven't used summary fields in a while, but it seemed pretty straightforward.
http://livedocs.adobe.com/flex/3/langref/mx/collections/SummaryField.html
This is actually a formatting example, but it contains all the code to create a summary row:
http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&productId=2&postId=11472
Actually, the simplest and easiest approach I found was having another ADG placed below the existing ADG. The new ADG will act like a summary row and hence will have only one row. After initializing the content ADG, we can render the cells of the summary ADG the way we want. Moreover, we can sync the horizontal scroll of the new summary ADG with the content ADG. so, in all it will actually be seen as the ADG with the summary row
Even though its actually not a summary row and one needs a lot of customizations, it does make sense to use this. :)

ASP.Net - Good UI Design Question for Managing large number of items

We're currently working on a solution that involves managing a large number of parts for a project. In our database, we have a project table and we have a parts table. Those parts can be assigned to multiple projects and vise-versa. This is done through a link table.
We're happy on the database side and it wont be changed, however we're a bit stuck on how to display the UI in a user-friendly intuitive way.
There are about 6000 parts (...at the moment) and we need to be able to easily assign/unassign these parts from a project quickly and easily.
Does anyone have any good examples of this?
I have always found real-time filtering to be pleasant to work with and narrow down things. This can require your users to be somewhat computer literate though...
Furthermore I would consider something with D&D. I would imagine two lists (one with projects and one with modules) where I can multiselect on either list and drag a single item from the other list to that selection.
And if it is going to be an interface that's going to be heavily/repeatedly used, consider good keyboard support. Me personally find that repetetive tasks can be done MUCH faster if they can be accessed by hotkeys.
Just thinking out loud ...
There are two distinct parts to this. The first is selecting parts and projects from the database and the second is associating parts to/from projects. You should try to avoid doing both actions in a single dialog.
From your post, it appears that parts can be assigned to projects and that projects can be assigned to parts. So, a wizard approach might work:
project or part?
/ \
select project select part
| |
show list of parts show list of projects
| |
add/remove parts to project add/remove projects to part
When showing a list of projects/parts, use a simple, sorted list with a filter box. Using a tree or other categorised system can be ambiguous for the user. For example, if the list was of foods and there were categories for fruit and vegetable, where would you put tomato? A shopkeeper would probably put in in vegetables whereas a botanist would put it in with fruits. So, a simple sorted list with a search box (like FF's about:config) works surprisingly well.
I'd try a number of things, from a pure UI point of view, if your collection falls naturally into categories, I'm a big fan of cascading lists or a sortable, filterable grid. (or both combined)
Your choice will depend on your users computer literacy as well as space or technology constraints.
If you can spare the space, I think that two lists, perhaps selected items on the left, and the collection of items on the right with affordances such as checkmarks or >> << buttons are great.
I'd probably take a page out of Excel's book, it has some perfectly workable examples of this sort of thing.
I'd also take the time to add multi-level undo, working with large datasets is an absolute pain as a user when you have no recourse for simple mistakes, it should ideally track and handle whatever fiddly interaction your user needs to make.

Resources