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

[Ronald O. <ous...@ci...>]

On 10-mrt-04, at 17:36, Donovan Preston wrote:

> A couple of questions about documentation and environment setup for 
> PyObjC 1.1:
>
> 1) I started reading the pyobjc documentation in earnest again last 
> night, and found myself editing it for spelling. I plan on reading 
> every last word and touching the documentation up, but I need to know 
> if there is a script I should run to generate the HTML before checking 
> in?

Thank you for proof reading. You don't have to generate the HTML, I'll 
do that before building the release files. If you really want to you 
can use Scripts/make_distrib.py, but that needs docutils and DocArticle 
(from the docutils sandbox).

>
> 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.

I've seen his announcement, but didn't look at it yet. We need at most 
two Xcode templates, one of simple applications and one for 
document-based applications. The 'Cocoa-Python-ObjC' variants are not 
relevant for Bob's PyMacApp.

>
> 3) Finally, the tutorial has some very ugly instructions about how to 
> locate NibClassBuilder in a variety of situations. Is there any way 
> this situation could be simplified? Perhaps the initial tutorial 
> should instruct users on how to build an application using an Xcode 
> template, and then only later introduce the shell commands for doing 
> the same. I know a shell script which invokes NibClassBuilder is 
> installed in the python bin directory, but this is not on the $PATH by 
> default. Should the installer make a symlink to this script into 
> somewhere that is on the $PATH?

nibclassbuilder is installed in /usr/local/bin when you use the binary 
installer. I'm going to create a PackMan database that will do the 
same. IMHO PackMan should automaticly use /usr/local/bin when 
installing source packages (this is easy enough when you use 
distutils).

>
> In general I would like to see the introductory documentation and 
> environment setup situation improved in time for the final 1.1, and I 
> am willing to spend the time to make this happen.

Thank you!

Ronald
--
X|support bv            http://www.xsupport.nl/
T:  +31 610271479       F:  +31 204416173