Re: [Pyobjc-dev] NibLoader.py: parsing nibs at runtime
Brought to you by:
ronaldoussoren
From: Just v. R. <ju...@le...> - 2002-11-16 20:53:17
|
Ronald Oussoren wrote: [ noop action stubs ] > If you choose to do nothing you might as wel write the empty method > yourself (there is probably a reason for doing nothing). That way we > can do away with the flag and always warn if you don't implement all > actions. Agreed. Will do. > > (I don't grok outlets just yet: are the default IBOutlet objects all > > that are > > ever needed, or are you supposed to provide them yourself?) > > The default IBOutlets are all that is ever needed. You can set specific > types in Interface Builder, but those are all Objective-C classes and > those are all represented the same way in the Objective-C runtime. Ok. I've renamed the NibInfo.printOverview() method to NibInfo.printTemplate(). It will print a Python template with stubs for actions and comments for outlets. NibLoader.py is converging back to classnib.py ;-) > I'd probably prefer to emit a warning when you do define IBOutlet > objects over doing it when you don't. Never warning at al is probably > best. > > BTW. outlets are implemented using attributes/member variables in ObjC > code, IBOutlets perform the same task in PyObjC. The thing that I don't understand is why they are class attributes: I'd expect (but then again, I don't grok them yet) they'd be specific to an instance, and therefore be instance attributes. How does it work? Just |