[Pythonmac-SIG] Re: Python for Mac apps...

[Peter Sommerfeld]

Hallo everyone !

I'm new on python and this list too. I have a follow up to  Gordon Worley's
msg.
I think about a cross-platform application with a medium duty GUI. Most of
it will
be structured text, outliners and something like this. There seems to be 2
options:

* to use the native function of the os direct via C or python libraries
either.
Obviously much more work than the second option.

* Tcl/Tk via tkinter. I'm not familiar with all that unix stuff and have
checked
some mac demos. Seems to be quite fast and powerfull even on my outdated PPC
603/75 Mhz. But this demos are very little applications. What's about more
enhanced requirements.  Are there any drawbacks ?

Other options ?

Jack Jansen wrote:
>Definitely. The reason I actually get the time to work on MacPython is
>that we
>use Python to develop a cross-platform multimedia editor and playback system
>for the new world-wide-web standard SMIL, GriNS. GRiNS has by now grown to
>about 50K lines, for all platforms (unix, win, mac) together, and the
>interface is pretty much native on all of these. It's definitely not as fast
>as it would have been when written in C, but it performs good on my (by now
>outdated) 133 Mhz machine, and it's even useable (though barely so) on my
>60Mhz 6100 or a fast 68040 machine. And in C it would be at least 10 times as
>much source, and definitely not doable with a team of 2 people and-a-bit.

Just van Rossum wrote:
>Check the IDE for an example of performance. It uses waste as a text engine
>(which is written in C) and uses many Toolbox features. Otherwise it's
>entirely written in Python. It's not too graphics intensive, though. It was
>noticably slower than a C/C++ app on my old Quadra, but still acceptable.
>It is not noticably slower on a G3...

Both of you decided to go the native way. May I ask for the reasons ?

Peter

- Lueneburg, Germany

PS: Is this list feasible for typical newby questions too ? I dislike to post
bulk like this to the main list.