I have the equivalent of 3 cascading data sources or drop down lists. Since all data has to be created up front will this be a good candidate for MonoTouch.Dialog as one item's data depends on the preceding value?
Example of what I'm trying to do: I have a list of client names and each client can have a list of projects and each project can have a list of tasks.
I like the UI of tables that MT.D creates. If MT.D is not suitable for this, what would be a good approach for getting a similar UI? Would I have to create a separate UITableView and data source for each item (Client, Project, and Plan) with only one row in it?
The UI that I'm trying to replicate is having a single rounded table cell with the type on the left (e.g. Client), an accessory indicator on the right, and once a value is selected have the value on the right.
Yes you can!. Just have a look at Touch.Unit source code on github.
It shows you the assemblies (first level), then the test fixture (second level) then the test cases (third level) and, if it fails, it will show you the failure details (on a fourth level).
All this is created dynamically when the assemblies are scanned to find [TestFixture] attributes on the types.
Even if this does not match exactly what you're looking for you'll see that customizing MonoTouch.Dialog is very easy. There are several questions (here on stackoverflow), samples (e.g. TweetStation) and tutorials on how to use it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With