Re: [Pyobjc-dev] NibLoader.py: parsing nibs at runtime

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

On Sunday, Nov 17, 2002, at 14:13 Europe/Amsterdam, Just van Rossum 
wrote:

> Jack Jansen wrote:
>
>> What I do wonder, though, is whether this should be in AppKit.
>> Shouldn't we try to keep AppKit clean, so the Apple documentation
>> completely describes it, and put our own PyObjC-specific stuff
>> elsewhere? There isn't a good place right now, I think, but now might
>> be a good time to add one ("PyObjC" comes to mind as a name). Or does
>> the objc package fit this bill?
>
> I agree with Jack. I also understand Bill's concern that
> NibLoader/NibClassBuilder is an AppKit only tool. That said, I think 
> it could be
> an options to _rename_ the objc package to PyObjC (or pyobjc, I don't 
> care
> much). This allows us to use that package _both_ as an interface to 
> objc as well
> as a collection of additional tools, that may or may not be specific 
> to AppKit,
> Foundation or whatever.
I'll have to put some more thought in this, but do want to add one 
point to the discussion: The module was named pyobjc before my rewrite. 
I dropped 'py' because I found it ugly and because it is not necessary.
>
> We should decide this pretty quickly, as I am with Bill that I think 
> we can
> expect a lot of interest to PyObjC in the near future, and the more 
> users are
> out there, the less we can afford such a change... And if we do rename 
> the objc
> package, that would be a great opportunity to review the names of 
> various other
> things as well. Eg. I don't think the python-style 
> all-lowercase-and-underscores
> fits particularly well with PyObjC, as all Apple's names use 
> [cC]amelCase. I
> would suggest (eg.) renaming lookup_class to lookupClass.
Good idea.


> A more religious issue (and therefore I shall not make a huge point of 
> it ;-):
Lets me get into my asbesteous suit before continuing...

>  I
> personally don't like spaces between parens in Python code. I can see 
> it works
> well for other languages, but IMO it doesn't fit Python at all. I'd 
> like to see
> foo(args) instead of foo( args ). A space _before_ an opening paren 
> _really_
> makes my stomach turn ;-)

That wasn't too bad, I feel the same. I also prefer to format my code 
in a simular way in C, with one minor variation: there whitespace 
between if/while/for and the following paren.

Now that we're discussing relegion: How about indendation. I currently 
use TAB to indent, but after looking through some PEPs recently I get 
the feeling that this is not the right way(tm) to format code. Should 
we reformat into 4-space indents?

Ronald