Re: Mail.app selection of front window
Re: Mail.app selection of front window
- Subject: Re: Mail.app selection of front window
- From: Paul Berkowitz <email@hidden>
- Date: Fri, 28 Mar 2003 14:08:27 -0800
On 3/28/03 12:52 PM, "Andrew Oliver" <email@hidden> wrote:
>
Not being a Cocoa developer, I don't know whether the fault lies in Cocoa
>
(and therefore Apple), or in the developers themselves, just that it
>
frustrates me when I see cumbersome workarounds to what should be
>
straightforward actions.
>
>
And I absolutely refuse to believe there's no way the Mail.app developer
>
team couldn't have implemented *some* way of getting the selected text in
>
the front window as an AppleScript object. That's just not a credible answer
>
and proposing that just insults the intelligence of every person on this
>
list.
>
>
Mac OS X has been public for 2 years now and it's about time that Apple got
>
their act together with regards to AppleScript, both in the core system and
>
in its own applications. AppleScript is touted as a significant USP that's
>
often profiled in Mac OS success stories, yet limitations like the one that
>
prompted this thread just make it look like a joke once people dig a little
>
below the glossy finish.
>
>
Maybe my posts do seem confrontational (heck, maybe they ARE confrontational
>
;) ), but please don't get me wrong. I love Apple, and AppleScript, I just
>
don't accept that incomplete dictionaries and half-assed implementations of
>
kludges are an acceptable way of moving the platform forwards. Blindly
>
accepting what comes out of Cupertino doesn't help anyone in the long run,
>
and if my posts make one person at Apple think for a minute, then I'm happy
>
(of course, I'd be happier if that person could do something about it... ;)
It is hard for cricket. He knows all this several times over, I'm sure
everyone in the AppleScript teams at Apple knows it. The main problem seems
to be that Cocoa AppleScript implementation - which is meant to be the thing
that makes it easy for all applications to be scriptable from now on - was
implemented with many flaws, back in OS 10.0.
The AppleScript engineers who know their stuff are probably extremely
annoyed with what the Cocoa engineers bequeathed to them, and signs are that
things will get fixed. Probably the AppleScript people like cricket can't
tell us publicly what they really think about what they were given and - who
knows - maybe their jobs would even be at risk if they did.
I hope that people higher up the chain know all about this situation. For
starters, I think it would be good if Sal Soghoian (who reads this list some
of the time, or could be forwarded Andrew's message) were to pass it on up
to Avie, or someone well-placed to do something about it.
It is a great frustration that things were done so poorly on the
applications' AppleScript end of OS X, and someone who could raise its
priority should be made directly aware of our feelings about it. It's not
really fair to attack cricket forcing him onto the defensive both about
things he may know deserve to be criticized as well as correcting mistakes
in the accusations.
So - if Chris E. or Sal is reading this - I would suggest that Andrew's
message would be a good one to forward on up the chain.
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.