Re: [Pyobjc-dev] NSApplicationMain idiom: wish to standardize

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

Ronald Oussoren wrote:

> I think this would be very usefull. However, I think this module
> should be in a seperate package to make it clear that this is a
> PyObjC helper module instead of wrapped Cocoa functionality.
> Foundation.Conversion should be moved to this package as well.
> 
> How about PyObjCTools?

Fine with me.

> - module PyObjCTools.Conversion would be the new name of 
> Foundation.Conversion
> - module PyObjCTools.AppHelper would contain your function and other 
> NSApplication related tools

Ok.

> Speaking of NSApplicationMain... Does anyone care to offer on opinion
> on the enormous amount of time between the call to NSApplicationMain
> and the call to awakeFromNib in a simple application? That period of
> time takes about 4 seconds of the 5 seconds my application needs to
> start up

I'm also still seeing long startup times, about 8-10 seconds. I'll
measure later how much of that is spent between NSApplicationMain() and
the first awakeFromNib call.

> (using a savagely butchered version of PyObjC, 'import
> AppKit' would use another 2 seconds if I hadn't build a mini module
> that exports all definitions I need from AppKit and Foundation).

Does this mean we should revisit the idea of replacing the Cocoa modules
with "lazy" module-like objects? If *you* are butchering up PyObjC that
should be a sign...

Just