Re: [Pyobjc-dev] Documentation generation, Xcode templates, locating NibClassBuilder

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

On Mar 10, 2004, at 8:36 AM, Donovan Preston wrote:
> 2) I would like to update the Xcode templates using Bob's new PyMacApp 
> main.m (I don't know if he announced it here, but he announced it on 
> the MacPython mailing list). How many varieties of templates should I 
> produce? The project builder templates had a bewildering variety of 
> project types you could create... Also, should I look into updating 
> the Project Builder templates, or is that too much of a can of worms 
> to try to open. I don't have 10.2 installed but I suppose I could set 
> up a 10.2 testing environment.

We need two templates:

Cocoa-Python Application
Cocoa-Python Document-Based Application

There is already a [mostly] working Cocoa-Python Application template 
in CVS.   It needs some refinement.   In particular, integrating Bob's 
new PymacApp main.m and general cleanup.   The Document-Based template 
is not really working yet.

In both cases, comparing to the "latest and greatest" templates as 
shipped by Apple would be useful to ensure that various settings, etc, 
are as close to the "pure ObjC Cocoa" templates as possible.   There is 
a python script included in the template tree that can filter an Xcode 
template into a normal project and back again;  that is, an Xcode 
template is just a regular project with markers throughout indicating 
where various programmatic substitutions should be made.

The one key difference between the default templates and the PyObjC 
Xcode templates is that I pushed keyword substitution into the NIB 
files, too [using the 10.2 and later text format].  The big win is NO 
MORE MyDocument.{nib,h,m}!!

The Cocoa-Python-ObjC template was simply a workaround for the lack of 
a linkable python runtime on 10.2.   It allowed the developer to push 
the ObjC code into a framework that was dyna-loaded at runtime.... no 
longer necessary.

b.bum