Saturday, November 22, 2008

Objective-C

In a glance, Objective-C is C plus object orientation and other fun little things.

Now being used to Java and C# for the last couple of years, this of course means one thing that I personally forgot very happily... pointers. But let's take it step by step.

Files and Headers

An Objective-C file has the file ending ".m", the header file has the file ending ".h"

To include the header files into your coding (be it source or other header files) you'll have to write "#import " for global headers (e.g. Cocoa.h) or "#import "headername.h"" for your own local headers. Besides the name (import <-> include) this is pretty much as in C++ (at least how I remember it :-) )

So starting of with, you would include the framework header file in your header file and your header file in your source file.

How Headers are setup

A header file normally includes an import for other headers and a class definition. The class definition consists out of the class name, its deriving object, its variables and its methods.

A simple class definition could look like this:


@interface AppController : NSObject {

int x;

}

@end

Now this class definition would not do to much as it does not have any methods, but it would define a class named "AppController" being derived from NSObject with one integer variable called x.


The definition always starts with "@interface" and ends with "@end"


A method definition in Objective-C will be defined like this:


- (int) setX:(int)y;


This defines a method setX with a return value of type int. To call the method you'll need to pass a variable of type int which can be accessed by the name y. The "-" in front of the method declaration is not a typo, but tells you that this is a "regular" instance method. A global class method would be defined with a "+" instead (comparable with the "static" keyword of Java/C#). The method definition will not be inserted into the curly brackets but between their end and the "@end" so the new class definition would look like this:


@interface AppController : NSObject {

int x;

}


- (int) setX:(int)y;


@end


The source file


To finish off our example here we'll have a quick look at the corresponding source file:


#import "AppController.h"

@implementation AppController


-(int) setX:(int)y

{

//Magic happens here.....

x=y;

return x;

}

@end

This should not be to much of a suprise now. Pretty much straight forward besides the "@implementation" and "@end" commands which simply wrap up the class related coding.

Sunday, November 02, 2008

Details on versioning

After the first steps in versioning I stumbled over some beginner's mistakes, I guess.
So let's walk through a quick project setup.

  1. Create a project in Xcode somewhere on your disk (you'll delete it later anyways....)
  2. Click on SCM in the Xcode menu, and then Repositories
  3. After selecting your Repository (mine is called Local Subversion), select the folder/branch where you want the project to be stored at
  4. Select Import in the toolbar
  5. Select the folder where the previously created project is located at and hit Import
  6. Xcode will tell you that the project got imported
  7. Now close the project and delete it
  8. Again go to the Repositores (step 2)
  9. Now click Checkout in the toolbar (don't click export like I did the first time... this will lead to a non-versioned copy of the project)
  10. Select the folder where you want the project to be stored at. This will be the working copy of the sources that you will work on.
  11. Hit Checkout
  12. Now you should have a copy on your desk. Next step is tell the project that it is a versioned project. Go to the project settings. On the very bottom of the properties page (in the General tab) you can now select the SCM repository. Select the repository that you would like to use.
  13. If you want to you can change the build output to some other directory.
  14. Afterwards you will see that the project file was modified as there is a capital "M" next to the project file (as long as you have selected the SCM preference by right clicking on the file listing)
  15. Now you can commit those changes back to the repository by clicking on "Commit Entire Project" in the SCM menu.
  16. That's it :-)