Re: [Pyobjc-dev] Objc-agnostic model classes
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2004-08-13 06:00:18
|
On 13-aug-04, at 2:01, Jordan Krushen wrote: > On 12-Aug-04, at 4:26 PM, Bob Ippolito wrote: > >> Having Python objects that don't inherit from NSObject cross the >> bridge doesn't work as well as it could. Personally I think that >> everything in PyObjC should support KVC unless explicitly told not >> to, especially bridged pure python objects. That's more up to bill >> and ronald though. > > Are you saying that this shouldn't be done this way at all (shim > PyObjC class -> pure python class), or that in the shim's getters, I > should convert the pure Python objects back into an NSSomething: > > def expectedRaise(self): > return NSNumber.numberWithFloat_(self.pyPerson.expectedRaise) > > def personName(self): > return NSString.stringWithString_(self.pyPerson.personName) Those are never necessary. When your strings contain non-ASCII values you have to convert them to unicode, but thats about it. > > If this shimming is what it takes, that's fine.. I'm mostly concerned > with how I can reuse the same model classes in Twisted and in PyObjC. > I do plan on having the model objects contain getters/setters to make > the shim classes easier, but I can't see how to have a pure Python > object support KVC without using objc.accessor or inheriting from > NSObject. Neither of which are pretty in a plaform-independent layer :-) Ronald -- X|support bv http://www.xsupport.nl/ T: +31 610271479 F: +31 204416173 |