Can anyone help me to solve this error??

BrianLachoreVPI said:

Please do not cross post in multiple forums. Thank you.

Click to expand...

dekan said:

Your attached image doesn't seem to resize to a point where I can actually see something. Not sure if that's just me here, but in case everybody has the same issue: You might want to make it so people can see what's going on.

Click to expand...

Nethfel said:

Just out of curiosity, is this your first application using iOS and ObjectiveC?

Usually you don't have variables sitting in the implementation like that (yes, I know that's common for Java, but in objective c, only static variables would be declared there (and those aren't very common unless you need the equivalent of class variables instead of instance variables which is usually reserved for counters or singletons))

You should be putting your IVars (like those MANY views that you can probably compress down into a single separate view controller) in the interface section. You also need to make sure to either #import the headers of those custom view controllers in the interface OR use @class for each of the classes in the interface and import the headers in the implementation.

Also, for readability - the generally used convention for naming in objective c is like this:

classes: each word that makes up the class name is capitalized

so psalm91viewcontroller would be Psalm91ViewController

variables (instance, local scope, global) and methods use what is known as camel case - first word of the name is lower case, remaining words are uppercase

so psalm91view would be psalm91View

Not that you have to do it that way, it is just the generally accepted naming technique used.

Click to expand...

Nethfel said:

You need to move those variables out of the implementation and into the header. Those errors are related to how those variables are declared at this point - get them out of the implementation and (unless your classes are named differently) the errors should go away as long as you use the @class directive OR import the headers for those other classes in the interface file.

I strongly suggest you either watch some tutorial videos on Objective-C and basic iOS development or get some books on the topic to help you get on solid ground with the basics.

If you have an ebook reader and want a quick get up and going book you might want to look at:

Objective-C 2.0 Essentials

and

iPhone iOS 4 Development Essentials (or the iPad iOS 4 Development Essentials)

as those books are very easy to follow and don't attempt to introduce too much in each portion of the chapters.

Without a good (or at least a decent) foundation, you're going to find that you'll have many problems like these due to not understanding the structure of the underlying code.

I'm not saying you can't do it - I have every belief that you can, you just need some more material to get you going

Click to expand...