4. C code compiles as Objective-C code

6. Implementing methods

7. Instantiating classes and objects

8. Invoking class and object methods

9. Protocols, categories, selectors, forwarding

10. Example of Objective-C Code

12. Is is a simple extension of C

14. It can be as high-level and flexible as Smalltalk if you use the object-oriented extensions

18. Mac OS X 10.5

19. Garbage-collection

20. Threading/Exceptions

21. Fast Enumeration

22. Properties

25. GNUstep

26. Writing Portable Objective-C Code On Apple Mac OS X , avoid Objective-C 2.0 syntax such as properties and fast enumerations. On Apple Mac OS X , avoid garbage collection and use explicit the traditional OpenStep reference counting. This is likely to change – GNUstep is getting garbage collection again. On both Apple and GNUstep , If you need to access the runtime, use an intermediate layer such as the one provided by gnustep-base additions.

27. History of Objective-C Core Frameworks

28. OpenStep API Specification (1994)

30. Basic data classes : NSString, NSNumber, NSData, NSNull

31. Collection classes : NSArray, NSDictionary, NSSet

32. Execution control classes : NSRunLoop, NSTimer, NSThread, NSLock

33. I/O classes : NSTask, NSFileHandle

34. Notification classes: NSNotification, NSDistributedNotification

35. Serialization classes: NSArchiver, NSCoder

36. Resource management classes: NSBundle, NSUserDefaults

37. Distributed Objects Classes: NSConnection, NSPort

38. And many more... Application Foundation Kit Application Kit Operating System OS Graphical System Objective-C Runtime

40. Menu classes : NSMenu, NSMenuItem

41. Basic drawing classes : NSView, NSColor, NSFont, NSGraphicsContext

42. Basic interaction classes: NSEvent, NSResponder, NSControl, NSCell

43. Control classes : NSButton, NSTextField, NSBrowser, NSPopUpButton, NSMatrix

44. Table classes: NSTableView

45. Text classes : NSTextView, NSTextStorage, NSLayoutManager, NSInputManager

46. Scrolling classes: NSClipView, NSSplitView, NSScrollView,

47. Standard panel classes: NSFontPanel, NSSavePanel

48. And many more... Application Foundation Kit Application Kit Operating System OS Graphical System Objective-C Runtime

49. Apple Cocoa Application Cocoa Foundation Kit Cocoa Application Kit Operating System (Apple Darwin/BSD) OS Graphical System Apple Objective-C Runtime

50. GNUstep Application GNUstep Base GNUstep GUI Operating System (Any!) Graphical System (Any!) GNU Objective-C Runtime GNUstep Back

52. OpenBSD, FreeBSD, *BSD

53. OpenSolaris, HP UX, other Unix systems

55. Writing Portable Objective-C Code On Apple Mac OS X , avoid Apple-only frameworks such as CoreFoundation, CoreSound, CoreAnimation, KeyChain, Carbon, Quartz, Quicktime, WebKit. On GNUstep , avoid GNUstep extensions that are not available as a separate library or framework that works on Apple as well.

58. Complete, total IDE

59. It uses its own files

60. Hard to work with developers who use other platforms where Xcode is not available

62. Similar to XCode

63. Lagging in features (this might change)

64. Uses its own files, then generates

65. gnustep-make GNUmakefiles

66. to build

68. even without a GUI

69. Makefile library designed to make building complex projects easy

70. Official building system for GNUstep

71. Very complete

72. Editable, portable text files

73. Requires editing text files - not a point-and-click GUI IDE include $(GNUSTEP_MAKEFILES)/common.make TOOL_NAME = hello hello_OBJC_FILES = hello.m include $(GNUSTEP_MAKEFILES)/tool.make

74. Building the Foundation Kit Example Not Portable Portable GUI IDE Text files include $(GNUSTEP_MAKEFILES)/common.make TOOL_NAME = hello hello_OBJC_FILES = hello.m include $(GNUSTEP_MAKEFILES)/tool.make XCode Project Center gnustep-make Pbxbuild can generate GNUmakefiles from Xcode projects

78. Apple has native linker implementation, GNUstep emulates them

79. Emulation can be inefficient/inappropriate on some platforms

81. Use GNUstep.h (eg, from Renaissance)

83. Menu Portability (hard) On Apple you must use the Apple-only method NSApplication -setAppleMenu: which is not part of OpenStep and not even declared in a public header (!!).

85. On GNUstep and Apple the standard organization of menus (location of menu items, etc) are very different.

87. It uses only the OpenStep API

88. It creates all the GUI in code

89. It has separate code to create the menu

90. on Apple Cocoa and GNUstep

91. It has a GNUmakefile and is built

92. using gnustep-make You can use it as an example of how to build a portable GUI in code .

97. Brilliant tool, extremely usable

98. and fast

99. It uses its own files (“Nib”s)

100. NIB files serialize GUI objects,

101. including platform-specific attributes such as fonts, sizes and colors

102. Static layout

103. Need to manually create a different NIB file for each language

105. Very similar to Interface Builder

106. Uses its own files (“Gorm” files)

107. Same pros/cons as Interface

108. Builder

109. Can import NIBs from Interface Builder (they might need manual adjustment after importing)

111. GNU LGPL framework

112. Open XML file format

113. Not that complete

114. Lacking a GUI builder

115. Editable, portable text files

116. Autolayout using boxes and grids

117. Can load up translations at runtime: a single file can support all

118. languages <gsmarkup> <objects> <window title=&quot;This is a test window&quot;> <button title=&quot;Print Hello!&quot; action=&quot;printHello:&quot; /> </window> </objects> </gsmarkup>

119. Creating GUIs without code Not Portable Portable GUI IDE Text files <gsmarkup> <objects> <window title=&quot;This is a test window&quot;> <button title=&quot;Print Hello!&quot; action=&quot;printHello:&quot; /> </window> </objects> </gsmarkup> Interface Builder Gorm Renaissance Renaissance GUI Builder (TODO)

121. Give constructive feedback, suggest improvements, provide patches

122. Create examples, tutorials

123. Write applications

124. Port existing applications back and forth between GNUstep and Apple Cocoa

125. Help improving GNUstep ports to Windows and

126. other platforms