I'm relatively new to iPhone Development and I'm trying to create an app that's using a UITableView that needs to push to different Views. Right now I'm designing it to push to a different page each time a cell is clicked. It seems that from other posts that I've read that it's not a good idea as there will be a lot of individual View pages. I'm not sure how to accomplish this as I am designing each View to have a phone number, email, web site and SMS that goes to different sources/destinations. I've designed everything up to this point and it works, but need this final step in order to finalize the app. Any help or tutorial that someone could be point me to would be appreciated.
I'll try to be more specific. I have a main menu of categories that navigates to a submenu of other categories. Each category that the submenu navigates to has a phone link, email link, SMS link, and web link. Do I have to make separate pages/views for each category or is there a way to make a NSDictionary that will house all of the data for each category that has the URL links?
You need to be more specific in your question. It sounds as if you wish to push a subsequent UITableViewController onto a UINavigationController stack using a 'push' segue, with the data passed to the sub-category using a combination of the methods 'didSelectRowAtIndexPath:' to determine the clicked row, and 'prepareForSegue:' to pass the row data to the new UITableViewController.
Check out the Apple tutorial - https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/SecondiOSAppTutorial/ which covers all of these concepts in very simple terms.
Related
I am creating a bible application. There are lots of chapters in the bible (e.g. genesis, exodus etc).
I created a button for each chapter loading. I load the verses and chapter in table-view cell. When the button is tapped it loads the next chapter and vise versa. I put the button in the footer of the table-view, but I want to change this functionality with pull down to refresh. I know pull down to refresh is used in many applications like Facebook and Twitter. I've also implemented this in my previous applications, but my need is to change the chapter when the user pulls down the table. When pulled down it changes to the next chapter.
I saw this functionality in the pocket-sword bible application; pull up for next chapter and pull down for previous chapter. How can I implement this in my application?
While that would work fine. I don't think it's the ideal implementation for navigation.
How would you go back to the previous chapter?
How would users know to pull down to go to the next chapter?
It just sounds and feels wrong.
I feel it would be better to implement swiping left and right to jump to the next page/chapter or even next/back buttons in either a navigation bar or toolbar. This is fairly standard.
Another option is to replicate the iBooks interface for jumping to chapters using the "paging bar" at the bottom (not sure what the correct name for it it)
we have to put same code thAT IS what code we used for directing next chapter in button-click,that code have to be put inside the _(void)refresh method.It automatically redirected to the next page when we pull down the table-view.What ever functionality we can add to this function.Thanks.
I'm creating an app and I need some help with design.
Launch Screen - I want to show 6-8 "category" buttons with labels loaded from an array ("normal" buttons from interface builder - not tab bar buttons or menu bar buttons).
Table Screen - When one of the category buttons is pushed on the launch screen, I want to show a table view with all of the items in that category.
Detail Screen - When one of the items on the table screen is selected, go to a new screen with details for the item. There will be an action button on this screen which will remove the item from the list if pressed.
My questions are as follows:
1) I don't want to show navigation buttons on the first screen. Can I still use a Navigation-Based application and hide the navigation controls on the first screen, or would it be better (easier) to create a view-based application and put a navigation controller "inside" one of the views? I'm totally open to any basic design approach suggestions you may have.
2) I've figured out how to create a sqlite3 file, add it to the project, query it, and generate the table view from the results, but I'm not sure about how to store the sqlite file in a way that will persist on the device when the user upgrades the app later. Any pointers on that?
Thanks for any help/links/documentation you can point me to. I've watched a million tutorials but none of the ones I've seen really address basic app design.
Now for Q1, both ways work fine but if you have buttons from the first screen, having a uinavigationcontroller might make it slightly easier if you plan to have back buttons on the screens after the first screen.
For Q2, to make the database persist when the user updates their app at some stage, simply keep the original database and include a new database (with a different name) with additional content, then modify your original database and import any additional content to it.
You can also do variations of that also, ie import content from old database to new database and etc. But the key is to keep the database file names different, ie add database_v1.sqlite, database_v2.sqlite and etc.
BTW don't forget to clean up any databases you won't use in future.
I have a task to write RSS reader for iOS.
For it I created navigation-based application.
I want to display list of RSS channels in the UITableView. When user clicks on one of this channels application must display list of items of chosen channel. What is better: use separated views with UITableView for RSS channels and for items, or display channels and items in single view and single UITable(if user wants to see channels, he see channels, if he wants to see items, he see items)? And maybe is there good code example of navigator-based application?
I don't quite understand what you're asking... However I can help you with your last question about the navigation based application. Here's a tutorial (I didn't create it) on how to use an RSS reader with a navigation controller: http://www.raywenderlich.com/2636/how-to-make-a-simple-rss-reader-iphone-app-tutorial.
Hope this helps.
Fellow stackers,
I am developing the interface for my iPhone application and I'm in doubt about an important paradigm that is present in almost every view I am making. I've read the Apple Human Interface Guidelines but I think that my question isn't answered there.
The problem is, e.g. in the "My Account" view I have to display all the kinds of content the user has created (Comments, Favorites, Notes, etc.). I am currently planning of displaying those as UITableViewCells in the main UITableView of "My Account": there will be a cell for Comments, that pushes the comment controller in the navigation controller, and so on for the other kinds.
One problem arises anyway: I've noticed that many applications use UISegmentedControls to accomplish the same task, and they seem to do so in a non coherent manner. Sometimes they use one method or sometime another. Is there a clear way of choosing one over the other? Or is it just personal preference?
I believe that there are situations where one is likely to be better than the other. As a personal rule of thumb, I avoid cluttering the current view with buttons that link to all the other available sections. I instead prefer an index where I can pick a section and have it load up that, then when I'm done, go back if need be.
So for example if you were using a tabcontroller to navigate between views like the "My Account" view, I would not use a UISegmentedControl. I would use a UITableView. This just allows for you to be more focused on the task at hand.
However, if you belive that your users will be flipping between sections in the account view more frequently, then maybe a semgented control would be the way to go for you.
i am starting my experience with iphone sdk. and i have a question, which is i am trying to create two pages to the app but i don't know how to link them or design them. like when i start the Xcode i find one page named View to design in it, i want to make that page a welcoming page then the user choose one of the three choices he see in that page. Once he clicked on one of them the program take him to the next page or the page he chose.
thank you
The standard approach on iPhone is a drill-down. Place a UINavigationController in your NIB, make the root-level view your welcome page. Then navigate to dependent views by invoking pushViewController on that navigation controller.
This is a very high-level description; you'd have to fill a lot of blanks. If you create a new project and specify a "navigation-based application", you'll get quite a bit of boilerplate code for this approach.
You really need a good book, I recommend Beginning iPhone 3 Development by Apress.
Take a look at using UIViewController's
- (void)presentModalViewController:(UIViewController *)modalViewController animated:(BOOL)animated
method. You can display your initial view, and when the user presses one of the buttons, display the intended view over top. If you build a new project, and choose "Utility Application" you will get some sample code for how this works.