IPhone Development - Switching Views

Question

First, let me mention that this post may be in the wrong forum, so if that is the case, please let me know to repost.
Next, my question is very simple. I have two views. The first has a button. The second has some text. I want to switch from the first, which loads when the app starts, to the second. This should be pathetically easy, but I have yet to figure out how it's done. At this point, their must be a fundamental problem with the way that I am thinking about how Windows and Views are managed, because based on my current beliefs, I cannot figure the rest out. I have created several "1-View" applications and, for what I am trying to do, have created several Views each of which do what I want them to do. But, I cannot find a way to switch from one to the other. I go to several homemade videos of people doing it, but no two people do it the same way and they all have their own little tricks to getting it done. This leads me to believe that it's not simply a matter of a lack of documentation by Apple, but that Apple doesn't even have a standard. Instead the have several hacked-together solutions that each can kind-of work depending on the situation.
Here is the way I am conceptualizing it and maybe someone can show me the error in my thinking. I create a View-based application for the iPhone. I believe that the AppDelegate class that is created for me appears to really just be a Window/View manager class in that it keeps track of the one and only Window and manages which View is currently being displayed in that Window. Then, there is the MainWindow.xib file which is really confusing, because it simply populates itself with whatever is in the ViewController.xib file. It's never even mentioned in any of the code I am given. I imagine it is mentioned elsewhere, but that is irrelevant.
Now, the ViewController.xib file is used along with Interface Builder to create a View from Widgets and link those Widgets' references and corresponding actions to class variables and methods in its corresponding ViewController.h and ViewController.m files. So, it would follow then, that if I wanted to create a second View, so that when a button on the first view was clicked a new, second View would be shown, I would create a new "View.xib" file and corresponding .h and .m files for it. Then, I have a method in my AppDelegate that takes a UIView object and removes whatever view is currently the subview of the window and adds the parameterized view as the new subview. This is also where I would put my transitions.
Now, the new View that I just created doesn't contain the Title Bar or whatever it's called where the battery monitor icon, carrier icon, etc. exist, so this means that whenever I am actually putting Widgets in the View I have to just remember to avoid it and that the "auto-alignment" thing is off. So, I try other options, and create a new "Window XIB". This blows my freakin' mind, because it appears to be what I want despite it being called a Window and not a View. So, I try the "Write Class File", and it creates a new class called UIWindow which is a subclass of UIView. But wait, aren't Views supposed to be what populates the Windows, and UIWindow is a class that already exists. AHHH!!!!
So, I rename the class to SecondView and create an instance of it in the AppDelegate. Now, I go into the AppDelegate.m file and change "window addSubview:viewController.view" to "window addSubview:secondView.view" (Edit: Brackets aren't allowed, so I am using quotes in their place here.) which doesn't compile, because it is a subtype of UIView which doesn't have a view member variable, only UIViewController does. So, I change it to make it a subclass of UIViewController which has a view member variable, and it compiles and shows a blank white screen of which neither of my views look like. Then, I go shoot myself in the face. It would appear that I need to link the new SecondView class to the SecondView.xib file somehow.
It appears that the AppDelegate class should manage nothing and should only have a single UIWindow object that it loads. Then, the View Controller which has a View object should really have an array of all Views and should populate its view object with the currently needed View. This would make sense except that of all the How-tos I have seen none of them do it this way. I am sure that I didn't say everything that I need to say, but at this point I am so infuriated that I cannot think straight.
<rant>
I have developed in several different environments, and I have never come across such a simple and common concept implemented in such a convoluted way. Maybe I am simply missing something obvious, here, but if that's the case, Apple please please please make the documentation far less cryptic. I feel like I'm walking blindly through a jungle when I try to read the How-to documentation on your site. If I need to know some information about some class then it is relatively easy to get to, but trying to figure out how to actually do something within iPhone development is painful.
I began trying to develop for the iPhone by just diving in and seeing what happened. That sort of failed, so I began reading your online help documentation and believe I took a step backwards. Finally, I bought a book on Objective-C that concluded with creating an iPhone app. I read it in a few days and now feel that I am rather proficient with the language as well as creating applications on the iPhone as long as they only consist of a single View in the ViewController class. All I want to do is switch from one View to another, and it shouldn't be this hard.
</rant>
Message was edited by: PhoenixRebourne

Answer 1

Well odds are you won't find what you are looking for here unless another developer happens to come here. These forums all withing the support area are user to user forums to help with issues of usage, repairs, etc.
Doesn't the developer area where you signed up to be a developer have forums?