Index: /trunk/source/examples/cocoa/nib-loading/HOWTO.html
===================================================================
--- /trunk/source/examples/cocoa/nib-loading/HOWTO.html (revision 8478)
+++ /trunk/source/examples/cocoa/nib-loading/HOWTO.html (revision 8479)
@@ -38,5 +38,5 @@
elements.
- InterfaceBuilder is an appliaction that ships with Apple's
+
InterfaceBuilder is an application that ships with Apple's
Developer Tools. The Developer Tools are an optional install
that comes with Mac OS X. Before you can use this HOWTO, you'll
@@ -114,9 +114,9 @@
The pathname is just a reference to the nibfile we want to
- load. The dictionary holds references to objects—the
- object that owns the nibfile (in this case, the running
- NSApplication object), and an array used to hold any toplevel
- objects in the nibfile. The zone is areference to the area of
- memory where the nibfile objects will be allocated.
+ load. The dictionary holds references to objects. In this
+ first simple example, we'll use it only to identify the
+ nibfile's owner, which in this case is the application
+ itself. The zone is a reference to the area of memory where
+ the nibfile objects will be allocated.
Don't worry if none of this makes sense to you; the code to
@@ -128,8 +128,8 @@
-
First, we'll get the zone from the running application. We'll
- tell Cocoa to allocate the nibfile objects in the same zone that
- the application uses, so getting a zone is a simple matter of
- asking the application for the one it's using.
+ First, we'll get a memory zone. We'll tell Cocoa to allocate
+ the nibfile objects in the same zone that the application
+ uses, so getting a zone is a simple matter of asking the
+ application for the one it's using.
Before we can ask the application anything, we need a
@@ -148,34 +148,33 @@
- ? (setf *my-app-class* (#_NSClassFromString (%make-nsstring "NSApplication")))
- #<OBJC:OBJC-CLASS NS:NS-APPLICATION (#x7FFF704C5C00)>
+ ? (setf *my-app*
+ (let* ((class-name (%make-nsstring "NSApplication"))
+ (appclass (#_NSClassFromString class-name)))
+ (#/release class-name)
+ (#/sharedApplication appclass)))
+ #<LISP-APPLICATION <LispApplication: 0x1b8de0> (#x1B8DE0)>
- Notice, by the way, that this form allocates an NSString
- object. We do it this way for the sake of simplicity, but it's
- not an example of good programming practice. NSStrings are
- foreign objects, allocated by the Objective-C runtime. They
- are not garbage-collected by Lisp, and so when you create them
- they hang around in memory until you manually deallocate them,
- or until you quit from Clozure CL.
-
- This simple example goes on to create several foreign objects
- by evaluating forms in the Listener, storing some of them in
- global variables. In this example, these objects are never
- deallocated. It's not a problem in such a small example; we
- just create a handful of objects at the Listener, and they are
- disposed of when we quit Clozure CL. But when writing real
- applications using the Objective-C bridge, you will need to
- learn to use Cocoa's memory-management discipline so that you
- can ensure that foreign objects are allocated and deallocated
- properly.
-
- Now that we have the application class, we can ask it for a
- reference to the running application:
-
-
- ? (setf *my-app* (#/sharedApplication *my-app-class*))
- #<LISP-APPLICATION (#x1B8E20)>
-
+ Let's review this form step-by-step.
+
+ First of all, it's going to store the returned application
+ object in the variable *my-app*, so that we have it
+ convenient for later use.
+
+ We need an NSString object that contains the
+ name of the application class, so the code allocates one by
+ calling %make-nsstring. The NSString
+ object is a dynamically-allocated foreign object, not managed by
+ Lisp's garbage-collector, so we'll have to be sure to release it
+ later.
+
+ The code next uses the class-name to get the
+ actual NSApplication class object, by
+ calling #_NSClassFromString.
+
+ Finally, after first releasing the NSString
+ object, it calls #/sharedApplication to get the
+ running application object, which turns out to be an instance
+ of LispApplication.
Voilà! We have a reference to the running Clozure CL
@@ -188,9 +187,7 @@
-
Now we have a reference to the application's zone. We can
- pass it
- to loadNibFile:externalNameTable:withZone: to
- tell it to allocate the nibfile's objects in the
- application's zone.
+ Now we have a reference to the application's zone, which is
+ one of the parameters we need to pass
+ to loadNibFile:externalNameTable:withZone:.
@@ -199,17 +196,20 @@
The dictionary argument
- to loadNibFile:externalNameTable:withZone: is used
- for two purposes. First, we use it to pass an owner object to
- the method. Some Cocoa objects need to have references to owner
- objects. For example, a window might need to check with an owner
- object to determine whether its fields and buttons should be
- enabled. You supply an owner object in the dictionary, under the
+ to loadNibFile:externalNameTable:withZone: is
+ used for two purposes: to identify the nibfile's owner, and
+ to collect toplevel objects.
+
+
The nibfile's owner becomes the owner of all the toplevel
+ objects created when the nibfile is loaded, objects such as
+ windows, buttons, and so on. A nibfile's owner manages the
+ objects created when the nibfile is loaded, and provides a
+ way for your code to get references to those objects. You
+ supply an owner object in the dictionary, under the
key "NSNibOwner".
-
The second purpose of the dictionary object is to collect
- references to any toplevel objects (such as buttons, text
- fields, and so on) that the runtime creates when loading the
- nibfile. To collect these, you pass an NSMutableArray object
- under the key "NSNibTopLevelObjects".
+
The toplevel objects are objects, such as windows, that are
+ created when the nibfile is loaded. To collect these, you
+ can pass an NSMutableArray object under the
+ key "NSNibTopLevelObjects".
For this first example, we'll pass an owner object (the
@@ -219,5 +219,8 @@
- ? (setf *my-dict* (#/dictionaryWithObject:forKey: (@class ns-mutable-dictionary) *my-app* #@"NSNibOwner"))
+ ? (setf *my-dict*
+ (#/dictionaryWithObject:forKey: (@class ns-mutable-dictionary)
+ *my-app*
+ #@"NSNibOwner"))
#<NS-MUTABLE-DICTIONARY {
NSNibOwner = <LispApplication: 0x1b8e10>;
@@ -235,6 +238,8 @@
- ? (setf *nib-path* (%make-nsstring (namestring "/usr/local/openmcl/trunk/source/examples/cocoa/nib-loading/hello.nib")))
- #<NS-MUTABLE-STRING "/usr/local/openmcl/trunk/source/examples/cocoa/nib-loading/hello.nib" (#x13902C10)>
+ ? (setf *nib-path*
+ (%make-nsstring
+ (namestring "/usr/local/openmcl/ccl/examples/cocoa/nib-loading/hello.nib")))
+ #<NS-MUTABLE-STRING "/usr/local/openmcl/ccl/examples/cocoa/nib-loading/hello.nib" (#x13902C10)>
@@ -243,7 +248,9 @@
- ? (setf *nib-path* (%make-nsstring (namestring "/usr/local/openmcl/trunk/source/examples/cocoa/nib-loading/hello.nib")))
- #<NS-MUTABLE-STRING "/usr/local/openmcl/trunk/source/examples/cocoa/nib-loading/hello.nib" (#x13902C10)>
- ? (#/loadNibFile:externalNameTable:withZone: (@class ns-bundle) *nib-path* *my-dict* *my-zone*)
+ ? (#/loadNibFile:externalNameTable:withZone:
+ (@class ns-bundle)
+ *nib-path*
+ *my-dict*
+ *my-zone*)
T
Index: /trunk/source/examples/cocoa/nib-loading/nib-loading.lisp
===================================================================
--- /trunk/source/examples/cocoa/nib-loading/nib-loading.lisp (revision 8478)
+++ /trunk/source/examples/cocoa/nib-loading/nib-loading.lisp (revision 8479)
@@ -25,4 +25,10 @@
(values load-succeeded-p context)))
+(setf *my-app*
+ (let* ((class-name (%make-nsstring "NSApplication"))
+ (appclass (#_NSClassFromString class-name)))
+ (#/release class-name)
+ (#/sharedApplication appclass)))
+
#|