Difference between revisions of "PasCocoa"

From Lazarus wiki
Jump to navigationJump to search
Line 524: Line 524:
# http://lapcatsoftware.com/blog/2007/11/25/working-without-a-nib-part-6-working-without-a-xib/
# http://lapcatsoftware.com/blog/2007/11/25/working-without-a-nib-part-6-working-without-a-xib/
* Code to create a menu without a nib file: http://trixul.cvs.sourceforge.net/viewvc/*checkout*/trixul/trixul/layout/cocoa/cocoamenubarimpl.mm?revision=1.6
* Code to create a menu without a nib file: http://trixul.cvs.sourceforge.net/viewvc/*checkout*/trixul/trixul/layout/cocoa/cocoamenubarimpl.mm?revision=1.6
==Articles about PasCocoa==
* Toolbox Magazine 2008, editions 5 and 6 (german language): http://www.toolbox-mag.de/archiv2008.html

Revision as of 17:12, 27 October 2008

PasCocoa is the project to build object oriented bindings to use Cocoa in Pascal.

Objective-C to Pascal Bindings

There are 2 main versions of Objective-C, and thus of Objective-C headers: 1.0 and 2.0

Version 2.0 is only available on Mac OS X 10.5 or superior, making it too restrictive at the moment, and thus the available headers are a translation of 1.0 headers from a Mac OS X 10.4.9 machine.

Objective-C 1.0 Bindings

  • Available on: Mac OS X 10.0 and superior

Objective-C 2.0 Bindings


<delphi> {

This example shows how to use the PasCocoa bindings to create a
NSAutoreleasePool, initialize the application global variable, create
a simple window without contents and attach a close handler to it that
exits the application.
Compilation of this example requires the following options:
-k-framework -kcocoa -k-lobjc
This example project is released under public domain
AUTHORS: Felipe Monteiro de Carvalho

} program simplewindow;

{$ifdef fpc}{$mode delphi}{$endif}


 objc, ctypes, FPCMacOSAll, AppKit, Foundation;


 Str_Window_Title = 'This is the title';
 Str_Window_Message = 'This is the message';


 { classes }
 pool: NSAutoreleasePool;
 MainWindow: NSWindow;
 MainWindowView: NSView;
 TextField: NSTextField;
 { strings }
 CFTitle, CFMessage: CFStringRef;
 { sizes }
 MainWindowRect, TextFieldRect: NSRect;


 {  Creates a AutoreleasePool for this thread. Every thread must have one }
 pool := NSAutoreleasePool.Create;
 { Creates the application NSApp object }
 NSApp := NSApplication.sharedApplication;
 { Creates a simple window }
 MainWindowRect.origin.x := 300.0;
 MainWindowRect.origin.y := 300.0;
 MainWindowRect.size.width := 300.0;
 MainWindowRect.size.height := 500.0;
 MainWindow := NSWindow.initWithContentRect(MainWindowRect,
   NSTitledWindowMask or NSClosableWindowMask or NSMiniaturizableWindowMask or NSResizableWindowMask,
   NSBackingStoreBuffered, NO);
 { Initializes the title of the window }
 CFTitle := CFStringCreateWithPascalString(nil, Str_Window_Title, kCFStringEncodingUTF8);
 { Adds a NSTextField with a string }
 CFMessage := CFStringCreateWithPascalString(nil, Str_Window_Message, kCFStringEncodingUTF8);
 TextFieldRect.origin.x := 0.0;
 TextFieldRect.origin.y := 200.0;
 TextFieldRect.size.width := 300.0;
 TextFieldRect.size.height := 100.0;
 TextField := NSTextField.initWithFrame(TextFieldRect);
 MainWindowView := NSView.CreateWithHandle(MainWindow.contentView);
 { Put's the window on the front z-order }
 { Enters main message loop }
 { Releases the AutoreleasePool for this thread }

end. </delphi>


svn co https://lazarus-ccr.svn.sourceforge.net/svnroot/lazarus-ccr/bindings/objc objc
svn co https://lazarus-ccr.svn.sourceforge.net/svnroot/lazarus-ccr/bindings/pascocoa pascocoa


Creating a class which inherits from a Cocoa class

To create a class which inherits from a Cocoa class, one needs to create a normal class which inherits from any of the classes on the PasCocoa bindings and use the NSObject.CreateClassDefinition method to register that class on the Objective-C runtime before calling the NSObject constructor.


<delphi> uses foundation;


 { TMyController }
 TMyController = class(NSObject)
   { Extra binding functions }
   constructor Create; override;
   function getClass: objc.id; override;


 Str_TMyController = 'TMyController';


constructor TMyController.Create; begin

 { The class is registered on the Objective-C runtime before the NSObject constructor is called }
 if not CreateClassDefinition(Str_TMyController, Str_NSObject) then WriteLn('Failed to create objc class');
 inherited Create;
 { Insert other desired initialization here }


{ Called by the NSObject constructor to get the definition of our class.

 At this point the class is simply identifyed by it's name and must be already registered
 on the Objective-C runtime. }

function TMyController.getClass: objc.id; begin

 Result := objc_getClass(Str_TMyController);

end; </delphi>

Registering Pascal methods as Objective-c methods

Pascal methods aren't automatically available to Objective-C. They need to be first registered on the Objective-C runtime by overriding the AddMethods method and calling NSObject.AddMethod method for every method to be registered.


<delphi> </delphi>


General Roadmap

Component Status Details
Objective-C 1.0 Runtime Headers Working Mac OS X 10.0 or superior
Objective-C 2.0 Runtime Headers Not Implemented Mac OS X 10.5 or superior only
Automatic headers Parser Partially Implemented
Foundation Partially Implemented
AppKit Partially Implemented

Foundation Classes Roadmap

Component Status
NSArray Working
NSAutoreleasePool Working
NSBundle Working
NSDate Working
NSGeometry Partially Implemented
NSObjcRuntime Working
NSObject Partially Implemented
NSRange Partially Implemented
NSString Working
NSValue Working
NSZone Partially Implemented

AppKit Classes Roadmap

Component Status
NSActionCell Partially Implemented
NSAlert Partially Implemented
NSApplication Working
NSBitmapImageRep Working
NSBox Working
NSButton Working
NSButtonCell Partially Implemented
NSCell Partially Implemented
NSControl Working
NSGraphics Partially Implemented
NSGraphicsContext Working
NSImage Working
NSImageRep Working
NSMenu Working
NSMenuItem Partially Implemented
NSNibDeclarations Partially Implemented
NSNibLoading Partially Implemented
NSOpenPanel Working
NSPanel Partially Implemented
NSResponder Partially Implemented
NSSavePanel Working
NSStatusBar Working
NSStatusItem Working
NSText Working
NSTextField Working
NSTextFieldCell Working
NSToolbar Working
NSToolbarItem Working
NSView Working
NSWindow Working

Implementation Details


The Cocoa headers contain several peculiarities that lead us to need a special structure for the bindings. First, several forward declarations of classes are done in a very unordently way. Pascal only accepts forward declarations of classes if they are all declared on the same type clause, and therefore a special session FORWARD is created to have a single forward declaration for each file.

The include file has a total of 4 separate sessions: HEADER, FORWARD, CLASSES and IMPLEMENTATION

A tipical include file should have this structure:

<delphi> {%mainunit appkit.pas} {

       Application Kit
       Copyright (c) 1997-2005, Apple Computer, Inc.
       All rights reserved.



//insert constants, records and other interface declarations with the exception of classes

{$endif} {$endif}

{$ifdef FORWARD}

 TNSClass = class;



//declaration of classes

 TNSClass = class(NSObject)

{$endif} {$endif} {$ifdef IMPLEMENTATION}

//insert implementation declarations here. The order is not important on the implementation, so don't use extra ifdefs.

{$endif} </delphi>



  • Inclusion of headers in other frameworks should be removed, because the each framework is mapped to a pascal unit, and therefore all include files of a used framework are already accessible. Inclusion of headers of the same file framework should become include clauses which will used a C-styled ifdef mechanism to resolve in which order the include files will be added. This mechanism works fairly well and keeps the structure of the include files similar to the original one.



  • Should include the same include files as the HEADERS section
  • All private members of classes should be removed


  • Method should send message using one of the functions:


objc_msgSend_frep (float and double types for i386, not for PPC)

objc_msgSend_stret (records)

Reference Page: http://developer.apple.com/documentation/Cocoa/Reference/ObjCRuntimeRef/Reference/reference.html

  • Class methods must be called for ClassID
  • Instance methods must be called for Handle

Type Encodings

Table of codes used for types when registering methods in the Objective-C Run-time Library:

c Char A character
i cint (ctypes unit) A C compatible integer
s cshort (ctypes unit)
l clong (ctypes unit)
q clonglong (ctypes unit) A long long
C cuchar (ctypes unit)
I cuint (ctypes unit)
S cushort
L culong
Q culonglong An unsigned long long
f Float
d Double
B ??? A C++ bool or a C99 _Bool
v None Indicates the absense of the parameter
* PChar A C-style string
@ id (objc unit) An Objective-C class instance
# Class (objc unit)
: Sel (objc unit) An Objective-C selector
[array type] An array
^type P<type> A pointer to type
? Pointer A generic pointer


Objects allocation

Objective-C language does not provide any special syntax to define, if class method is construtor method or not. However, Apple provides some kind of methods naming convention, you can learn more about it here: http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/Articles/chapter_13_section_3.html

Following Objective-C methods, should be constructors for Pascal objects:

  • class methods named +(id) alloc... (Obj-C construct methods)
  • class methods +(NSClassName *) anyMethodName... (Obj-C convenience constructors)
  • class methods +(id) anyMethodName (Obj-C convenience constructors)
  • instance methods name - init... (Obj-C initialization methods).

Though object allocation and initialization are separated in time for Objective-C. Pascal rarely uses the same style, providing larger number of constructors, so - init... methods should become constructors, though it's questionable.


Objective-C provides mechanism to extend class methods dynamicly without need of class iheritance. These are known as categories and extensions. Reference page: http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/Articles/chapter_4_section_1.html This feature is not supported by Pascal, there's no way to extend methods of the class without inheritance.

Categories are used very often in Cocoa headers. They are used to group methods logically. It's common, that Base class is extended with several categories within a single header file. The good example is NSString.h, there base NSString class has only 2 method, while it's categories declares dozens of new methods.

In this case (if base class and it's categories are declared in the single header) all methods of the categories must be declared the base class. So convertede Pascal class NSString, would contain all methods that were declared in NSString.h categories.

The same way, might be used to generate Pascal classes, if base Obj-C class and it's categories are declared in different headers, but discouraged.

Carbon-Cocoa integration

Some Obj-C classes can be casted to Carbon types, such types are also known as toll-free bridged. It's recommended to use Carbon types (all of them declared at FPCMacOSALL unit) for parameters and method result types.

<delphi> function GetName: NSString; procedure SetStrParam(value: NSString); </delphi>

should be <delphi> function GetName: CGStringRef; procedure SetStrParam(value: CGStringRef); </delphi>

List of toll-free bridged types, add additional information on Carbon-Cocoa integration can be found at this page: http://developer.apple.com/documentation/Cocoa/Conceptual/CarbonCocoaDoc/Articles/InterchangeableDataTypes.html

Unnamed enums

There're great number of unnamed enums declared in Cocoa headers. These enums are used to describe the constant values for methods parameters. They must be converted as Pascal constants, rather than enumeration, to avoid parameter size conflicts.

Cocoa related external links

  1. http://lapcatsoftware.com/blog/2007/05/16/working-without-a-nib-part-1/
  2. http://lapcatsoftware.com/blog/2007/06/04/working-without-a-nib-part-2-also-also-wik/
  3. http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/
  4. http://lapcatsoftware.com/blog/2007/06/17/working-without-a-nib-part-4-setapplemenu/
  5. http://lapcatsoftware.com/blog/2007/07/10/working-without-a-nib-part-5-open-recent-menu/
  6. http://lapcatsoftware.com/blog/2007/11/25/working-without-a-nib-part-6-working-without-a-xib/

Articles about PasCocoa