I am currently developing a new iOS app which is basically a decision tree app. All the data comes from an XML file (list of questions and logic path depending on answers). The XML reading is not a problem.
I know I could develop this by hardcoding everything in the storyboard, but I don't find this efficient. Design-wise, I don't know where to start to sort of build the storyboard dynamically. What stops me is that, based on what the user answers, some paths have different number of levels (or questions); so different storyboard screens.
Any help would be much appreciated!
You may want to build your views "manually" from code.
Related
I've seen much of the apple documentation, many examples, and some github projects.
http://www.raywenderlich.com/16873/how-to-add-search-into-a-table-view
and
http://www.appcoda.com/search-bar-tutorial-ios7/
are ios 7 only.
https://developer.apple.com/library/ios/samplecode/TableSearch_UISearchController/Introduction/Intro.html
is confusing with a lot of unnecessary clutter complicating it.
http://www.raywenderlich.com/76519/add-table-view-search-swift is for swift only, but seems to be exactly what I need if it someone could translate it to objective c.
I don't get it at all.
If someone could just tell me step by step the differences, or maybe a simple breakdown, that would help.
It seemed to be a lot easier in ios 7, why did they change it?
Even when I drag a search bar controller in the storyboard editor, and link it to my header, the default property and name is uisearchdisplaycontroller which is deprecated.
I also have another question that can't easily be googled:
If I have a table view, it's easy to know what was selected.
But when I select or edit the search results,
how do I know what to do to the table view array, if the index paths will be different?
I currently have an iPhone app thats uses xib's as the graphical interface.
We are planning to make an iPad app using the same code, but with a completely different graphical interface.
I really like storyboards because of the nice flow and overview and was thinking of using it only for the iPad, but I'm also considering not to because:
Is it bad practice to have one for iPad but not for iPhone?
The seque and push/present can probably be confusing?
Having more developers in a storyboard can give merge nightmares?
Thanks in advance
Is it bad practice to have one for iPad but not for iPhone?
If you continue to use only XIBs, do the same for both if its a universal app. It will be confusing for others who may work on your code. And you might end up with a lot of if else code.
The seque and push/present can probably be confusing?
Once you get used to it, its really a useful way of navigating between controllers. If you have any specific questions do point it out.
Having more developers in a storyboard can give merge nightmares?
Its just a XML document, any versioning system out there can handle merges pretty easily. As with any file if two or more developers have worked on same piece of code (in this case can be color change, layout change) then yes it will get conflicted. And developers should be in sync. If one dev is changing the whole structure of the controllers then yes it will be a nightmare. You need to wait and get the latest working copy and ammend your changes.
And you dont have to put all eggs in one basket. You can have multiple storyboards as well.
I am planning to develop my first app in Cocoa. I have been collecting ideas for the UI and have settled in with the design very similar to iPhoto (i.e. library style or 'shoebox' application as referred by Apple's programming guide). In a nutshell I need master detail kind of setup like in iOS (iPad's UISplitview).
To achieve this should I put a NSSplitview and on the left panel have a NSTableView and on the right panel have a NSCollectionView?
Are there any examples/boilerplate or tutorials for creating app in OS X?
Your instincts are correct. You might decide eventually you want something more customizable that an NSCollectionView, but it’ll get you started fast and you can do most of what iPhoto does with it. (You can’t do rows with varying #s of items on them, like Delicious Library does, unless you write your own view.)
I am new here and new to iOS, so my apologies in advance if my question is silly.
I have just finished a course on iOS and Xcode and learnt how to build the different types of apps, like master-detail, tabbed or single view applications.
My question is : Is it possible to build an app that would be for example a master-detail app but would look like a tabbed one on one of the views and would look like a page-based on another view? In other words is it possible to create an app that would be a mix of several types ? I have Googled everywhere but I can't find anything. I may be using the wrong key words as on the top of that, I am French. I am not looking for precise explanations, just if somebody could point me in the right direction where to look and continue studying.
Thanks in advance and have a nice day.
Well am not sure if this is exactly what you are looking for but you can take a look at this example. Its a combination of UISplitViewController & UITabBarController
Custom UISplitViewController for iPad
I need to create a iOS app where the main screen is very similar to the Facebook iOS App. I am using a UITableView to show the different posts in the feed. My question is:
What is the best option to implement this? One option is to insert Textviews/Imageviews/labels to the table view cell and another option is to have one UIWebView in each table view cell.
I have to show a lot of pictures and texts, so maybe html will be easier.
Any experience?
If you have to show a lot of pictures and text, adding one complexity level (like HTML) is not gonna help.
I'd suggest to start researching on how you can speed that huge table up, and how to retrieve the content you want to display on each cell. For instance, you could use a parallel thread that would retrieve the content in the background as you scroll down and would store it in a cache so it doesn't have to be done several times. RestKit or (depending on your specific needs) AFNetworking are surely of some help in your case.
Also, have a look to this article (a bit old, but still interesting!) on how improve your scrolling speed: Fast scrolling (and link to github example project)