Forum

[Alex.be]

Sorry it was sarcasm. I do believe that posts like these should not be answered. At least not in this manner. There are more and more completely clueless users asking very basic questions on these forums, drowning the few interesting subjects with questions that have either been answered over and over again, or especially now demonstrate a total lack of ability to read even the simplest of documents or procedures or even the most basic programming knowledge.

Understand me, I welcome all new users to the community, and the more of us the better, but I do feel that it is everybody's duty to observe a minimum of patience before posting any question, and understanding than instead of getting things done by other people it will be
- faster
- more effective
- the ONLY way
to read and experiment and understand the documentation.

Basically, if you can't write a loop, there is no amount of posting to these forums, however detailed the answers, that will make you ever get something accomplished. You have to absorb a minimal set of information by yourself or eveyr single step of your development will be a road block. Through that kind of trial and error it would take years to get a GUI hello world done.

If you don't know where to start, type "objective-c" and "cocoa iphone tutorial" in google.

I am open to criticism if this reply is seen as elitist, though I would like to believ that it would be salvatory instead of perpetuating the idea that you can get things done by asking questions to the community when you encounter a problem. It should ALWAYS be a last resort, not even not to distrurb said community, but because it will be 1000 times more efficient to
1. read and assimilate various amount of documenttion while looking for an answer
2. learn to solve problems by yourself.
3. Google is your friend for 99% left unanswered - developping good search skills and several sources of information is crucial. It will always be faster than wait for an answer from a human on the forums, especially since the more general the question (thus when it hasnt been researched) the less useful the answer in actual code terms (sure now you can use a loop, but you still don't know when to use one, what iterators are, when to use a while, how to write an inverse loop, how to break in special cases, etc... all of which would take you 5 minutes to find out if you typed "obective-c loop syntax in google" and read the first 5 links, discard the 2 worst, bookmark the best one, read, understand, assimilate, learn, rinse, repeat...)