On 12 Jun 2007, at 16:17, Jack Jansen wrote:
> You missed EasyDialogs, which is also the one we may want to keep.
> It uses aepack for the file dialogs.
Yep, didn't notice the 'import' statement buried down in the body
there. I agree that ED should stay, at least for now. I'll see about
sub
has wrote:
> In the longer term, EasyDialogs definitely needs to be substantially
> rewritten
shouldn't EasyDialogs be re-written to use Cocoa? Or would that require
the full pyObjC package -- speaking of which is that ever going to be
part of the 'standard" MacPython package?
I suppose it co
On Thursday, June 14, 2007, at 06:57PM, "Christopher Barker" <[EMAIL
PROTECTED]> wrote:
>has wrote:
>> In the longer term, EasyDialogs definitely needs to be substantially
>> rewritten
>
>shouldn't EasyDialogs be re-written to use Cocoa? Or would that require
>the full pyObjC package -- speak
Ronald Oussoren wrote:
> That's unlikely, I have no plans for trying to get pyobjc in the
> stdlib.
Fair enough -- I don't really like platform dependent stuff in the
standard lib anyway.
> It might be useful to make MacPython a kitchensink distribution of
> Python for Mac OSX instead of just th
On Thu, Jun 14, 2007 at 01:16:08PM -0700, Christopher Barker wrote:
> However, if was nice to have some stuff without any external
> dependencies -- is there a lightweight way to do just Easy Dialogs,
> without all of PyObjC?
It shouldn't be hard to simply wrap a Cocoa EasyDialogs implementation
On Jun 14, 2007, at 1:21 PM, Nicholas Riley wrote:
> On Thu, Jun 14, 2007 at 01:16:08PM -0700, Christopher Barker wrote:
>> However, if was nice to have some stuff without any external
>> dependencies -- is there a lightweight way to do just Easy Dialogs,
>> without all of PyObjC?
>
> It shouldn'
