Python and MacosX [Matthew's Journal]

You're viewing

emperor's journal
Create a Dreamwidth Account Learn More

Reload page in style: site light

←

→

I want to write an Xwrits-alike for MacosX, since Coffeebreak is a)shareware b)crap.

Now, assuming I could find out how to compile C programs against bits of carbon (which I hope is just RTFM) without using Xcode, it'd be a fairly easy bit of C programming, but I'd really like to do this with python.

But. The Carbon interface to python is completely undocumented, and I don't think I'm really l33t enough with Carbon to be able to bullshit my way through installing event handlers and the like.

What should I do? Anyone caught suggesting perl will be shot.

Mood::

geeky

←

→

There are 14 comments on this entry. (Reply.)

perl!

[link] [reply]

Ow! NopleaseSTOP agh agh agh croak.

[link] [parent] [reply]

*fx*: shoots

senji

[link] [parent] [reply]

Ow.

Ow ow ow.

Ow.

[link] [parent] [reply]

Bugger! you beat me to it!
*sigh*
not that I understood a single sentance of the post except the last two... Oh, and the metasentance 'But.'.

[link] [parent] [reply]

Personally, my first port of call would be wxPython, since that's what I'm familiar with. But it's a bit of an overkill, I would think. Tkinter might be more appropriate—I can't remember whether it's included with Apple's install, but if not it's readily available with MacPython. I believe it's also got better documentation.

[link] [reply]

Are you sure you don't mean Cocoa? Carbon is the old Classic Mac API which you probably don't want to use unless you have to. (Cocoa is the Objective C thing that AIUI drives the Aqua GUI and all that jazz.)

(S)

[link] [reply]

The only thing I've *had* to do with Carbon is the hotkey interface (nabbing a key combo, whatever application is in the foreground when it's hit). And that's perfectly usable in the middle of a Cocoa app. Otherwise, Carbon really is more for porting old Mac code (and/or coding expertise), at least IMO.

So, isn't there a Python/ObjC bridge through which Cocoa could be used with some degree of sanity and documentedness? (Mind, it'll be a different experience without InterfaceBuilder, but there's no reason why it can't be done.)

[link] [reply]

There is, as

mobbsy pointed out. I think I'm just too used to gtk and fiends, where you could do the whole jing-bang-lot without leaving emacs, and then just type "make" :)

[link] [parent] [reply]

"The most important usage of this is writing Cocoa GUI applications on Mac OS X in pure Python."
http://pyobjc.sourceforge.net/

[link] [reply]

You could port Workrave to Mac ;) </fangirl>

[link] [reply]

Can't you just compile Xwrits? MacOSX does support X11, right? Or does it want some obscure X extension that isn't supported?

[link] [reply]

I suspect that if you did, it would only be able to keep track of what you were up to in X11 apps, rather than in other OS X apps, wouldn't it? I think

emperor uses X11 a little more than I do, but hardly exclusively...

[link] [parent] [reply]

antinomy says, that would only catch X11 events, which given I do quite a lot of work not within X11 would rather miss the point...

[link] [parent] [reply]

Sun	Mon	Tue	Wed	Thu	Fri	Sat
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25 1
26	27	28	29	30	31

Matthew's Journal

Python and MacosX

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

(no subject)

October