pyobjc-dev

[Pyobjc-dev] nswindow subclass

[Gus M. <gu...@mu...>]

I searched the archives for "nswindow", so apologies if this has
already been answered already...

I created a new Cocoa-Python Application, compiled it and it worked
fine, I then wanted to see if I could make the window a custom one (for
some silly ideas I've got).. so I created a custom class called
PydgetWindow that extended NSWindow, and made the Window instance in the
MainMenu.nib file a custom class of the same type (PydgetWindow).

However, when I try and run it, I get the following message:
"Unknown Window class PydgetWindow in Interface Builder file,
	 creating generic Window instead"

This technique works out fine for a regular objc project, is this
something that is possible with pyobjc ?

thanks,

-gus

-- 
"Christmas means carnage!"  -- Ferdinand, the duck

Re: [Pyobjc-dev] nswindow subclass

[<bb...@ma...>]

On Tuesday, Feb 11, 2003, at 15:02 US/Eastern, Gus Mueller wrote:
> However, when I try and run it, I get the following message:
> "Unknown Window class PydgetWindow in Interface Builder file,
> 	 creating generic Window instead"

Assuming that PydgetWindow is implemented in a python file, did you 
load the file/module before the NIB file was loaded?

That is, are you sure that the class is defined prior to loading the 
NIB file?

You can simply add 'import PydgetWindow' in __main__.py [assuming that 
is the name of the source file]...

b.bum

Re: [Pyobjc-dev] nswindow subclass

[Gus M. <gu...@mu...>]

bb...@ma... (bb...@ma...) wrote:
> On Tuesday, Feb 11, 2003, at 15:02 US/Eastern, Gus Mueller wrote:
> >However, when I try and run it, I get the following message:
> >"Unknown Window class PydgetWindow in Interface Builder file,
> >	 creating generic Window instead"
> 
> Assuming that PydgetWindow is implemented in a python file, did you 
> load the file/module before the NIB file was loaded?
> 
> That is, are you sure that the class is defined prior to loading the 
> NIB file?
> 
> You can simply add 'import PydgetWindow' in __main__.py [assuming that 
> is the name of the source file]...

It wasn't a python file, it was a compiled objc class.. but I did what
you described, and that worked just fine.

But now I'm slightly curious why the other way didn't work.  Maybe I'll
play with it a little bit more.

thanks,
 
-gus

-- 
"Christmas means carnage!"  -- Ferdinand, the duck

Re: [Pyobjc-dev] nswindow subclass

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

Gus Mueller wrote:

> > You can simply add 'import PydgetWindow' in __main__.py [assuming
> > that is the name of the source file]...
> 
> It wasn't a python file, it was a compiled objc class.. but I did
> what you described, and that worked just fine.
> 
> But now I'm slightly curious why the other way didn't work.  Maybe
> I'll play with it a little bit more.

That's because the app as you compile it is merely a wrapper that starts
a new process. (Read the main .m file for details and look for execve.
For the _reasons_ of this, check the list archives...)

I _think_ what could work is building a minimal C extension that
contains the class and import that. While that's definitely more work
than adding a .m file to your project, it can probably be streamlined
with a template. I haven't heard of anyone who actually _did_ this, but
I don't see why it wouldn't work. Would be nice to find out, though...

Just