As far as adding the text field goes, I think adding an entire new view controller is probably the wrong way to go. You should be able to manage the whole process from the EAGLView -- since this is where most of your logic probably is, including whichever code tracks the games current state.
Since I don't know all the details of your project, this is really just a "thinking aloud" list of suggestions.
* Views are displayed in hierarchies. Your EAGLView is just another view in this respect. You'll probably want to add the UITextField as a subview under it. (You'll notice a degradation in performance when you do, but I'm guessing you won't be wanting to do much else while the user is entering their score.)
* Adding just the UITextFieldDelegate methods needed to the EAGLView controller shouldn't add much bloat to the code. You may only need to implement textFieldShouldReturn: and textFieldDidEndEditing:.
* So you'll need a "getPlayerName" method to create the textField, add it as a subview, and make it first responder (which makes the keyboard appear); an implementation of textFieldShouldReturn: to check the player entered something and if so, get the textfield to resign first responder (which dismisses the keyboard); and an implementation textFieldDidEndEditing: to remove and destroy the textfield and do something with the input.
Like I said, this is just a rough outline of the approach I would take.
__________________
SimCap - Simple iPhone and iPad Simulator screen capture
|
