First, you can find out if any application (or control panel) is scriptable by choosing the 'Open Dictionary' option. If the application is displayed in the 'Open' dialog then it is scriptable (and you'll be able to see a list of the AppleScript commands it supports). If the application is not scriptable (as is the case with the Extension Manager) then it won't appear in the Open dialog.
Your simplest option is to get a copy of Conflict Catcher from
Casady & Greene. It's like an Extension Manager on steroids and is scriptable:
Code:
Conflict Catcher Suite : Events supported by Conflict Catcher.
Select Set: Select the specified startup set.
Select Set string
[Restart boolean] -- Should Conflict Catcher restart after selecting the set?
About Conflict Catcher: Display Conflict Catcher’s about box.
About Conflict Catcher
Enable Startup File: Enables the specified startup file.
Enable Startup File string
folder string
Disable Startup File: Disables the specified startup file.
Disable Startup File string
folder string
Create System Report: Create a system report to the specified file.
Create System Report file specification -- where to create the report
Alternatively, of course, you could write your own (at least in as much as moving items to/from the (disabled) folder) although you wouldn't be able to directly handle the startup control in AppleScript.
IMHO your question raises one of my biggest gripes with Apple. They should follow the old adage 'Eat your own dog food' and actually implement some of their own technologies in their own products. Imagine what you could do if every one of the standard Control Panels and Extensions that ships with the OS has some level of scriptability.
[This message has been edited by Camelot (edited 10-16-2000).]