\section{\module{gensuitemodule} ---         Generate OSA stub packages} \declaremodule{standard}{gensuitemodule}  \platform{Mac}%\moduleauthor{Jack Jansen?}{email}\modulesynopsis{Create a stub package from an OSA dictionary}\sectionauthor{Jack Jansen}{Jack.Jansen@cwi.nl} The \module{gensuitemodule} module creates a Python package implementingstub code for the AppleScript suites that are implemented by a specificapplication, according to its AppleScript dictionary. It is usually invoked by the user through the \program{PythonIDE}, butit can also be run as a script from the command line (pass\longprogramopt{help} for help on the options) or imported from Pythoncode. For an example of its use see \file{Mac/scripts/genallsuites.py}in a source distribution, which generates the stub packages that areincluded in the standard library. It defines the following public functions: \begin{funcdesc}{is_scriptable}{application}Returns true if \code{application}, which should be passed as a pathname,appears to be scriptable. Take the return value with a grain of salt:\program{Internet Explorer} appears not to be scriptable but definitely is.\end{funcdesc} \begin{funcdesc}{processfile}{application\optional{, output, basepkgname,         edit_modnames, creatorsignature, dump, verbose}}Create a stub package for \code{application}, which should be passed asa full pathname. For a \file{.app} bundle this is the pathname to thebundle, not to the executable inside the bundle; for an unbundled CFMapplication you pass the filename of the application binary. This function asks the application for its OSA terminology resources,decodes these resources and uses the resultant data to create the Pythoncode for the package implementing the client stubs. \code{output} is the pathname where the resulting package is stored, ifnot specified a standard "save file as" dialog is presented tothe user. \code{basepkgname} is the base package on which this packagewill build, and defaults to \module{StdSuites}. Only when generating\module{StdSuites} itself do you need to specify this.\code{edit_modnames} is a dictionary that can be used to changemodulenames that are too ugly after name mangling.\code{creator_signature} can be used to override the 4-char creatorcode, which is normally obtained from the \file{PkgInfo} file in thepackage or from the CFM file creator signature. When \code{dump} isgiven it should refer to a file object, and \code{processfile} will stopafter decoding the resources and dump the Python representation of theterminology resources to this file. \code{verbose} should also be a fileobject, and specifying it will cause \code{processfile} to tell you whatit is doing.\end{funcdesc} \begin{funcdesc}{processfile_fromresource}{application\optional{, output, 	basepkgname, edit_modnames, creatorsignature, dump, verbose}}This function does the same as \code{processfile}, except that it uses adifferent method to get the terminology resources. It opens \code{application}as a resource file and reads all \code{"aete"} and \code{"aeut"} resourcesfrom this file.\end{funcdesc}