public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nathan <nathan.stocks@gmail.com>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] The road ahead?
Date: Tue, 1 Nov 2005 12:14:11 -0700	[thread overview]
Message-ID: <96c9d6a80511011114g73ce283al7a66faa0e019375f@mail.gmail.com> (raw)
In-Reply-To: <e36b84ee0511011103w644356f0i5353607b7209c6cd@mail.gmail.com>

On 11/1/05, m h <sesquile@gmail.com> wrote:
> There's also pyobjc which allows integration of python and cocoa....

That's true!  I wanted to look into that a long time ago, but not
knowing python nor cocoa at the time, I decided not to.  I'm now
decently fluent in python.  Do you happen to know how much
Cocoa/Object-oriented C you have to know to use pyobjc?

I've been itching to create something with a GUI for a decade
now...just  for fun.

-- 
gentoo-osx@gentoo.org mailing list



  parent reply	other threads:[~2005-11-01 19:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 22:17 [gentoo-osx] The road ahead? dirk.schoenberger
2005-10-31 23:12 ` Kito
2005-10-31 23:49   ` dirk.schoenberger
2005-11-01  7:33     ` Grobian
2005-11-01 16:07 ` Nathan
2005-11-01 16:28   ` Kito
2005-11-01 16:55     ` Nathan
2005-11-01 17:17     ` Grobian
2005-11-01 18:09       ` Nathan
2005-11-01 19:03         ` m h
2005-11-01 19:13           ` Grobian
2005-11-01 19:32             ` m h
2005-11-01 19:36               ` Grobian
2005-11-01 19:45                 ` m h
2005-11-01 19:14           ` Nathan [this message]
2005-11-01 16:57   ` dirk.schoenberger
2005-11-01 17:26     ` Grobian
2005-11-01 18:08     ` Nathan
  -- strict thread matches above, loose matches on Subject: below --
2005-11-01 19:35 dirk.schoenberger
2005-10-30 10:49 Grobian
2005-10-30 17:15 ` Stroller
2005-10-31  5:25 ` Lina Pezzella
2005-10-31 18:58   ` Grobian
2005-10-31 18:52 ` Kito
2005-10-31 19:34   ` Grobian
2005-10-31 21:42     ` Kito
2005-10-31 22:20       ` Grobian
2005-11-01 22:45     ` Lina Pezzella
2005-11-02  0:06       ` Kito
2005-11-02  7:29         ` Grobian
2005-11-01  0:16   ` m h
2005-11-01  0:32     ` Brian Harring
2005-11-01  0:59       ` Kito
2005-11-01 19:16         ` m h
2005-11-01 20:10           ` Kito
2005-11-01 20:16             ` Nathan
2005-11-01 20:21               ` Grobian
2005-11-01 20:37                 ` Kito
2005-11-01 20:45                   ` Grobian
2005-11-01 20:58                     ` Kito
2005-11-01 21:05                       ` Grobian
2005-11-01 22:01             ` m h
2005-11-01 22:55               ` Kito
2005-11-04 17:50                 ` m h
2005-11-08  1:48                   ` m h
2005-11-08 16:53                     ` Grobian
2005-11-08 17:09                       ` Kito
2005-11-08 21:10                         ` m h
2005-12-05  5:19                           ` m h
2005-12-05 17:20                             ` Kito
2005-11-02  2:33             ` Brian Harring
2005-11-02  3:00               ` Kito
2005-11-02  4:12                 ` Brian Harring
2005-11-02  4:16               ` Nathan
2005-11-02  5:52                 ` Brian Harring
2005-11-01  1:20       ` m h
2005-11-01  1:57         ` Brian Harring
2005-11-01  0:51     ` Kito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=96c9d6a80511011114g73ce283al7a66faa0e019375f@mail.gmail.com \
    --to=nathan.stocks@gmail.com \
    --cc=gentoo-osx@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox