Hear us Roar
Article:
 |
|
Embedding F-Script into Cocoa Applications
|
| Subject: |
|
thanks, I believe # is F-scripts symbol and have distilled something |
| Date: |
|
2002-08-12 22:12:01 |
| From: |
|
psheldon
|
Response to: thanks, example gave something to chew on
|
My objC.pdf manual with index didn't mention a #.
I got, p.57 of old objC.pdf manual with index, that a method selector can take a runtime assigned variable as an argument, so I understand why you value implementing F-Script to take something like a literal constant. I've seen constant strings and string variables that were assigned, so I think I got the idea what this #-construct is doing and how its place could be occupied with something more general.
You wrote :
"The target-action paradigm is described in the Apple Objective-C book, as well as some notions about outlets."
I read this, but I need to struggle writing to get it in my heart.
An outlet is an object declared in a controller associated with an IB object. The IB/controller object has methods that the controller can send it as messages, such as to write some text. Now, when I set up such an outlet and its use totally in F-Script and interface builder, I imagine I must exemplify me doing something to get that object to do its method. To get an idea, I give myself an example of pushing a button. That button would run a script by my coding as in your example and in that script the outlet would be assigned to and object by the control drag mechanism. Then I would see the text print.
Am I right?
If I am right, when I am not so tired, I will give myself an exercise doing this in a simple little example program. I shall then write myself a little column, big enough for my own adventure. I know I can talk myself into believing I understand, but only when I try to work out something will I get the ultimate confidence (after some frustration).
I shall consider buying Cocoa book by Hillegass.
Thank you again.
|
Showing messages 1 through 1 of 1.
-
Re: thanks, I believe # is F-scripts symbol and have distilled something
2002-08-14 10:54:48
pmougin
[View]
|
| |
First, you let know the F-Script interpreter about the button by control-dragging FROM the F-Script interpreter object TO the button and assigning the button to one of the interpreter outlet (object1 for instance).
Now, you can manipulate the button from within F-Script. This means that you can now type "object1 setTarget:[sys log:'hello'. sys beep]. object1 setAction:#value:]" in the F-Script live mode window. This will establish the block [sys log:’hello’. sys beep] as the target of the button.
Phil