Re: [Pyobjc-dev] Reason not to use the python based main

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

bb...@ma... wrote:

> I ran into the single biggest reason not to use a pure python main this 
> morning.  Project Builder's indexing relies on the use of header files 
> to determine what to index.  As such, if I link Cocoa, AppKit, and 
> Foundation into my application as I build main.m, all three framework's 
> documentation and headers will be fully indexed by PBX such that I can 
> easily and very quickly access it through cmd or opt double-clicking.
> 
> Very, very handy.

Hm, basing a coding decision on one specific feature of one specific IDE?
Bleh...

> Now, of course, this doesn't mean we couldn't use a python based main 
> and provide a different NSExecutableFile key/value in the information 
> bundle while continuing to build a binary with all the frameworks for 
> indexing purposes, but why bother when we already have a 
> bin-python-main.m that works quite well, if fully Cocoa compliant, and 
> has some additional features already implemented that are extremely 
> convenient as the size of a project grows?

- the current main.m doesn't work if the python executable isn't /usr/bin/python
- it's 50 lines of dense Obj-C code instead of 5 sparse lines of Python
- the executable can't easily be created from a template
- it depends on dev-tools being available, can't be built from pure Python
- why would one _ever_ want to use Obj-C if the same can be done in Python and
  speed is not an issue?

Questions:
- what's not Cocoa-compliant about the current Python solution?
- what are the additional features of main.m?

Just