Re: [Pyobjc-dev] buildapplication strawman

[Jack J. <Jac...@cw...>]

On Tuesday, Nov 19, 2002, at 18:06 Europe/Amsterdam, Just van Rossum 
wrote:
>> Yes, it's added to the resources. Ah, I now see your "The .lproj or
>> individual nibs should then be listed as a resource" sentence. So you
>> want the user to pass the main nib twice, once as a file and once as
>> a name. Hmm, yes, with nibs in ..lprojs I can see the point. Ok, fine
>> with me, but you should probably add a check that the main nib
>> actually exists.
>
> I read your code, and it just picks an arbitrary nib if there are more 
> than one,
> I don't quite understand how you can defend that...

No, not an arbitrary one, it picks the first one you specified. But 
never mind:
let's do this your way (i.e. specify the nib by name, separate from the 
.plist
files).

>> But unfortunately the __rawmain__ trick is needed for one of the most
>> useful applications of an applet: taking a standard unix Python
>> script and turning it into a droplet.
>
> Don't you want to move the argv emulation to Python as well? It's 
> hairy stuff
> and I think we could win a great deal to have it in Python. I really 
> think we
> should strive to use a vanilla main, and the execve wrapper makes it 
> all
> possible.

Let me borrow Guido's time machine .... [POOF] Done!

PythonW uses the normal unix main program (as of 2.3a0, not in 2.2.X). 
And the __rawmain__
is all about doing the OSA stuff for argument emulation.

Look at Mac/Lib/appletrawmain.py (which is copied to __rawmain__ in an 
applets that wants
argv emulation) and argvemulator.py (which does the actual work).
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -