[Pythonmac-SIG] package structure for OSA interfaces

[Jack Jansen]

On Tuesday, January 22, 2002, at 02:15 , Michael J. Barber wrote:

>> I think we can do one better, even: define these events in a magic, 
>> handwritten suite (StdSuites._builtin_Suite comes to mind) and use 
>> this as the base class for both StdSuites.Standard_Suite and 
>> StdSuites.Required_Suite. These latter two are then still generated, 
>> and there's a one-line bit of magic in gensuitemodules that recognizes 
>> we're reading an AETE (not AEUT) for standard or required and inserts 
>> the magic baseclass.
>>
>> Would this do the trick?
>
> Hmm, depends on some implementation details that I'm not so sure of. 
> Let me make sure I understand the distinction between AEUT and AETE. 
> Checking a bit with ResEdit seems to indicate that AETE goes with 
> applications and AEUT is in the AppleScript extension (and possibly 
> elsewhere?). If that's the case, shouldn't the magic baseclass get 
> inserted for AEUT, and for AETE gensuitemodule just grabs 
> StdSuites.Standard_Suite and StdSuites.Required_Suite, so that the only 
> difference is in how the StdSuites package is generated?

Absolutely right. I had apparently reversed AEUT and AETE: AEUT is 
indeed OSA-supplied and AETE is the application-supplied extension.
--
- Jack Jansen        <Jack.Jansen@oratrix.com>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -