? (setf *my-app*
- (let* ((class-name (%make-nsstring "NSApplication"))
- (appclass (#_NSClassFromString class-name)))
- (#/release class-name)
- (#/sharedApplication appclass)))
+ (let* ((class-name (%make-nsstring "NSApplication"))
+ (appclass (#_NSClassFromString class-name)))
+ (#/release class-name)
+ (#/sharedApplication appclass)))
#<LISP-APPLICATION <LispApplication: 0x1b8de0> (#x1B8DE0)>
@@ -159,102 +159,102 @@
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.
*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.
%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.
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 - application object! Now we can ask it for its zone, where it - allocates objects in memory:
- -- ? (setf *my-zone* (#/zone *my-app*)) - #<A Foreign Pointer #x8B000> -- -
Now we have a reference to the application's zone, which is
- one of the parameters we need to pass
- to loadNibFile:externalNameTable:withZone:.
The dictionary argument
- 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 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
- application object), but we don't need to collect toplevel
- objects, so we'll omit
- the "NSNibTopLevelObjects" key.
- ? (setf *my-dict*
- (#/dictionaryWithObject:forKey: (@class ns-mutable-dictionary)
- *my-app*
- #@"NSNibOwner"))
- #<NS-MUTABLE-DICTIONARY {
- NSNibOwner = <LispApplication: 0x1b8e10>;
- } (#x137F3DD0)>
-
-
-
- Now that we have the zone and the dictionary we need, we
+ 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 + application object! Now we can ask it for its zone, where it + allocates objects in memory:
+ ++ ? (setf *my-zone* (#/zone *my-app*)) + #<A Foreign Pointer #x8B000> ++ +
Now we have a reference to the application's zone, which is
+ one of the parameters we need to pass
+ to loadNibFile:externalNameTable:withZone:.
The dictionary argument
+ 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 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
+ application object), but we don't need to collect toplevel
+ objects, so we'll omit
+ the "NSNibTopLevelObjects" key.
+ ? (setf *my-dict*
+ (#/dictionaryWithObject:forKey: (@class ns-mutable-dictionary)
+ *my-app*
+ #@"NSNibOwner"))
+ #<NS-MUTABLE-DICTIONARY {
+ NSNibOwner = <LispApplication: 0x1b8e10>;
+ } (#x137F3DD0)>
+
+
+
+ Now that we have the zone and the dictionary we need, we can load the nibfile. We just need to create an NSString with the proper pathname first:
-- ? (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)> -- -
Now we can actually load the nibfile, passing the method +
+ ? (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)> ++ +
Now we can actually load the nibfile, passing the method the objects we've created:
-- ? (#/loadNibFile:externalNameTable:withZone: - (@class ns-bundle) - *nib-path* - *my-dict* - *my-zone*) - T -- -
The window defined in the "hello.nib" file should appear +
+ ? (#/loadNibFile:externalNameTable:withZone: + (@class ns-bundle) + *nib-path* + *my-dict* + *my-zone*) + T ++ +
The window defined in the "hello.nib" file should appear
on the
screen. The loadNibFile:externalNameTable:withZone:
@@ -263,7 +263,31 @@
returned NIL.