Key Value Observing - Revision history

Cbv: add category

2006-10-23T14:50:43Z

add category

Stefan Urbanek at 08:35, 9 March 2005

2005-03-09T08:35:29Z

Stefan Urbanek: added pseudo-implementation

2005-03-09T08:35:06Z

added pseudo-implementation

RFM: Key Value Observing ideas

2005-03-02T15:01:01Z

Key Value Observing ideas

New page

Stefan Urbanek wrote:

Is anyone working on the Key-value observing?

I've just been updating KVC and thinking about KVO

http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueObserving/index.html

In the documentation one can read:

"Automatic key-value observing is implemented using a technique called
isa-swizzling.

The isa pointer, as the name suggests, points to the object's class which
maintains a dispatch table. This dispatch table essentially contains pointers
to the methods the class implements, among other data.

When an observer is registered for an attribute of an object the isa pointer of
the observed object is modified, pointing to an intermediate class rather than
at the true class. As a result the value of the isa pointer does not
necessarily reflect the actual class of the instance.
"

Is it difficult to implement it in GNUstep?

No more than in MacOSX.

If not, what is needed?

If noone is working on it and if someone skilled knows how to implement it or
has some hints, please write notes for others here:

OK, see below ...

1. You need to write a class to manage observing of objects (call it GSKVN for instance).
This class neeeds to have instance variables to hold -

a. a class pointer

b. information about all observers of the object and what sort of notifications they want to get.

2. You need to create a lock protected NSMapTable which will contain pointers to observed objects as keys, and instances of the KVN class as values.

When you start observing an object, you create an instance of the GSKVN class usaing NSAllocateObject(),
and store it in the map table.

Within the GSKVN instance, you store the class of the object being observed.
You change the isa variable of the object being observed to be a pointer to the GSKVN class.

Now, when a message is sent to the original object, it actually gets sent to the GSKVN class.
This class doesn't implement the method, but it does implement things like -respondsToSelector:, -methodForSelector: -methodSignatureForSelector: and forwardInvocation:

So, the implementations of these methods in the GSKVN class will -

a. use the map table to look up the GSKVN instance corresponding to the object being observed.

b. use the class pointer stored in the GSKVN instance to look up methods and dispatch messages,
intercepting those of interest and sending out notifications.

There are obviously a few other special cases -
If the observed object receives a -dealloc message, the GSKVN instance must also remove itsself from the map table.
If the observed object receives a -class message, the GSKVN instance must return the original class pointer.
etc.

When there are no longer any observers watching an object, the GSKVN instance for the object is removed from the map table.

When the GSKVN object is removed from the map table, it must be deallocated using NSDeallocateObject()

Finally, the big special case ...
When an observed object receives a -respondsToSelector: or -methodForSelector: etc message for a selector corresponding to an accessor method which is not implemented by the class of the observed object, the GSKVN class needs to have -respondesToSelector: return YES if there is an instance variable corresponding to it, and -methodForSelector: must return a method which is able to access the instance variables accordingly (looking at the _cmd argument to see which instance method to acccess). This is messy, but fairly strightforward.

One thing worth noting ... information for this case should be assembled when the object is first observed ... by examining all the ivars of the object and seeing whether corresponding accessor methods exist. There are two reasons for this -

1. performance ... you don't want to do that sort of thing often.

2. so that the appropriate selectors for the fake accessor methods can be registered with the runtime
otherwise the KVC system would be unable to attempt to access the ivars via accessor methods, and might attempt to access them directly ... which would mean that the notification systtem would be unaware of changes.

Hope that this helps.

← Older revision		Revision as of 14:50, 23 October 2006
Line 152:		Line 152:

	Hope that this helps.		Hope that this helps.
		+
		+
		+	[[Category:Objective-C]]

@@ Line 102: / Line 102: @@
            target->isa = originalClass;
            [observedProxies removeObject:self];
-−
            /* FIXME: somehow release and dealloc self */
+       }

@@ Line 39: / Line 39: @@
 b. information about all observers of the object and what sort of notifications they want to get.
 . You need to create a lock protected NSMapTable which will contain pointers to observed objects as keys, and instances of the KVN class as values.
-When you start observing an object, you create an instance of the GSKVN class  usaing NSAllocateObject(),
+When you start observing an object, you create an instance of the GSKVN class  using NSAllocateObject(), and store it in the map table.
 Within the GSKVN instance, you store the class of the object being observed.
 You change the isa variable of the object being observed to be a pointer to the GSKVN class.
 Now, when a message is sent to the original object, it actually gets sent to the GSKVN class.