Re: [Pyobjc-dev] NIB Validation & action methods

[Just v. R. <ju...@le...>]

[bbum]
> > Given that action method validation already exists within the AppKit 
> > framework and it works at the only time where complete/correct 
> > validation is possible, why should we bother duplicating that 
> > functionality in the PyObjC module and doing so in a fashion that is 
> > going to generate false warnings?

I would be easy to avoid these false warnings by (manually) adding a stub
action.

[Ronald Oussoren]
> It might generate false warnings if the Python code adds new methods at 
> runtime. Whenever I do things like that I prefer not to depend on 
> automatic mechanisms likes Just's AutoBaseClass.

Right.

Currently AutoBaseClass adds stub actions, basically disabling the AppKit
validation, so I think this should be removed.

Btw. is it possible to mix in action methods from another class like so:

class PyModel(AutoBaseClass, NSTableSource, SomeCommonActionsIPreparedEarlier):
    ...

? If this _is_ possible, then the stub-injecting code currently in
NibClassBuilder will only screw things up...

Ok, the stub actions need to go. Then remains the question whether (in addition
to AppKit's own warnings) it may be useful to issue a warning on missing actions
here as well.

Just