>>Does anyone have any thoughts on how third-party scripting apps like Script Debugger will handle the update?
I'm betting that Mark Aldritt is on top of this and SD will be ready. >>I have only been scripting part-time for about six months, so this may not mean as much to me for a while. Would this mean that coercing data to Unicode may not be necessary in Leopard?
That's the reason I thought it was important enough to post to the list. There was a significant amount of bandwidth in the last few weeks devoted to handling text coercions to and from Unicode.
It may be that whatever effort we put into that now will be redundant within a week.
>>has> Thus, I'm pretty certain that apart from the ability to type Unicode characters directly in Script Editor we'll see only minor superficial changes, with the significant changes being largely under the hood.
>>>Apart from being a non-trivial functional improvement for once (although I'm sure many of AppleScript's other longstanding deficiencies remain), such a change is unlikely to be 100% compatible with existing scripts (i.e. anything that requires old-style strings), in which case a major version change would definitely be indicated.
>>>Let endless exchanges of expert-sounding but entirely valueless pontifications now commence
While agree that 100% compatability is not realistic, I think Apple does a pretty remarkable job keeping scripts from breaking with new releases.
I have scripts still being used that I wrote for system 7.1. working in OS X 10.x
ES
=
|