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 submitting a patch in the next few days - it won't be a big job to fix. In the longer term, EasyDialogs definitely needs to be substantially rewritten or removed sometime within the next couple of major Python releases as it lacks things like Unicode and long string support and uses some ancient APIs that almost certainly won't exist on 64-bit. The file dialog APIs might be okay, and I think CFUserNotification could replace most of the rest with minimal effort - the only one that might need a bit more work is the progress dialog. Also, if ED does end up getting rewritten, there may be an argument for redesigning the API, which is pretty crusty, doesn't follow standard conventions, and probably doesn't take full advantage of the functionality provided by the more modern OS X APIs. Not much point doing anything until Leopard is out though. has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
