I came across something else i use in my obj-c apps that I cant\nseem to find any documentation about doing with titanium. Input\nfields inside an alert. I use it for a account register dialog\n(much easier and imo smoother progression).
\nhere an example of how its done in objective c
\n\nUIAlertView *alert = [[UIAlertView alloc] initWithTitle: @\"Register Account\" message: @\"\" delegate: self cancelButtonTitle: @\"Nevermind\" otherButtonTitles: @\"Register!\", nil];\n[alert addTextFieldWithValue: @\"\" label: @\"Email\"];\n[alert addTextFieldWithValue: @\"\" label: @\"Password\"];\n[alert addTextFieldWithValue: @\"\" label: @\"Password Confirm\"];\n\nemailField = [alert textFieldAtIndex:0];\nemailField.keyboardType = UIKeyboardTypeAlphabet;\nemailField.keyboardAppearance = UIKeyboardAppearanceAlert;\nemailField.autocorrectionType = UITextAutocorrectionTypeNo;\nemailField.autocapitalizationType = UITextAutocapitalizationTypeNone;\n \npasswordField = [alert textFieldAtIndex:1];\npasswordField.clearButtonMode = UITextFieldViewModeWhileEditing;\npasswordField.keyboardType = UIKeyboardTypeNumbersAndPunctuation;\npasswordField.keyboardAppearance = UIKeyboardAppearanceAlert;\npasswordField.autocorrectionType = UITextAutocorrectionTypeNo;\npasswordField.secureTextEntry = YES;\n\npasswordField2 = [alert textFieldAtIndex:2];\npasswordField2.clearButtonMode = UITextFieldViewModeWhileEditing;\npasswordField2.keyboardType = UIKeyboardTypeNumbersAndPunctuation;\npasswordField2.keyboardAppearance = UIKeyboardAppearanceAlert;\npasswordField2.autocorrectionType = UITextAutocorrectionTypeNo;\npasswordField2.secureTextEntry = YES;\n\n[alert show];\n[alert release];\n\nany chance we might see this in the future as well?
Part of the problem is that the -[UIAlertView\naddTextFieldWithValue:label:] and -[UIAlert textFieldAtIndex:] are\ncurrently undocumented/private APIs, and the use of it could result\nin App Store rejections. There's another trick that's just as hairy\nwhich involves blindly stabbing UITextFields into the view that is\nUIAlertView.
That's unfortunate. I've seen apps on the appstore that employ\nthis method, but you know how crappy apples policies are... they\ncould get pulled tomorrow, or never. :(
Tell me about it. My 'favorite' is when you release 2.0, which\nhas x new feature and gets approved, then you do an important\nbugfix to 2.0.1, and it's rejected for the x which was in 2.0.\nGiven the trouble Apple gave PhoneGap early on, Titanium was\ndesigned to stay as safely inside the lines as possible.
\nThe Apple guidelines themselves say, 'don't put text fields in\nalerts, use modal fullscreen pages for it'. The fact that Apple\nthemselves do it (Safari and app store) and have such a nice\ninterface for it makes this even more annoying.
\nIn the mean time, the solution is to create a window with a web\nview with the text fields and buttons, and have\nwindow.open({modal:true}) so the window is brought up from the\nbottom. It's not as pretty, but it's kosher and it's here now.
\n--Edit: My bad. I can't recall, but I think the {modal:true}\nfunctionality is coming out in 0.7.
No longer holding breath for Apple to share their toys with\nothers. Until they do, we might as well close this one. Since it\nwas never resolved, it'll have to be marked invalid.
This is really something I been wishing for a long long time.\nAny way someone can make this thing as a module so its optional? I\nwant to test it with an app and see if it gets rejected!
This is really something I been wishing for a long long time.\nAny way someone can make this thing as a module so its optional? I\nwant to test it with an app and see if it gets rejected!