On Mar 2, 2005, at 1:02 PM, has wrote:
It's already there, so it's not going anywhere in 2.4. The
justification is that people *did* ask for an OSA wrapper -- I
believe you were one of the larger proponents.
No, I wanted a Python OSA component. Different thing. The only person
I know was asking
Hi,
I've written a small appscript that exports an iPhoto album using the
"album" photo album tool (written in Perl, but I don't have time to
rewrite it... :-/). I wrote the Python script and installed it as
/Library/Scripts/Applications/iPhoto/iphoto2album so I can use it from
the global Scripts
On Mar 2, 2005, at 16:02, has wrote:
Bob wrote:
It can't happen until Python 2.6 at the earliest. I don't think
it's very likely to go away anyway. Good luck!
Why so long? Merely refactoring the distribution doesn't break
backwards compatibility so I don't see why the reorganisation
couldn't b
Bob wrote:
If you learn bgen and submit proper patches
Without proper documentation and tutorials? Sorry, but masochistic
self-flagellation is not my thing. This is somebody else's house of
cards to sort out before everyone else can seriously be expected to
play in it.
Yet you screw around with
On Mar 2, 2005, at 9:51, has wrote:
Bob wrote:
If you learn bgen and submit proper patches
Without proper documentation and tutorials? Sorry, but masochistic
self-flagellation is not my thing. This is somebody else's house of
cards to sort out before everyone else can seriously be expected to
pl
On 3/2/05 6:00 AM, "has" <[EMAIL PROTECTED]> wrote:
>> In this case, the API *asks* for an Alias. So, yeah, you do
>> actually want an Alias.
>
> No, the TextEdit dictionary says 'alias', but the dictionary is
> merely documentation, not the API itself, and dictionaries are
> regularly incorrec
Bob wrote:
Absolutely. I have no problem with mistakes being made. It's
setting them in stone that's the trouble.
Not stone, just molasses.
Near enough as makes no practical difference. It's a situation that
should not occur in the first place. These molasses are entirely
man-made.
If you lear
Bob wrote:
FSSpec is legacy. It should not ever be used in any code except to
reference nonexistent files or to deal with legacy APIs. You
shouldn't use them if the API will take an FSRef or an Alias.
Neither FSRef or Alias can be used to refer to non-existent files.
FileURL does, but I'm not
