【正文】 n Automation Server. For more information, see... GISDK Mechanics Language Elements Resources 1 GISDK Mechanics GISDK provides a powerful means for creating, testing, and installing addins, custom applications, and server applications. This section contains technical information on GISDK and how it works, including essential reference information. For more information, see... The Platform and the UI Database Compiling Resources Working with the GISDK Debugger Installing GISDK Applications Accessing TransCAD as an Automation Server The Platform and the UI Database To a user, TransCAD is a program like any other Windows program. To a GISDK developer, however, TransCAD has two distinct parts: the platform and the user interface (UI). ?? The platform is the core set of geographic information system (GIS) and database management system (DBMS) capabilities that are used to make maps and perform analysis. ?? The user interface (UI) is the set of menus, dialog boxes, toolbars, and toolboxes that provide a user with access to these capabilities, along with the GISDK instructions that are followed when a menu item, toolbar, toolbox, or dialog box option is chosen. The platform is contained in the executable program file () and the various dynamic link libraries (DLLs) and other files that support it. The UI is stored in a database, called the UI Database. The UI Database for TransCAD is named GIS_UI and contains the following 4 files: , , , , , , and . The platform and the UI Database are inseparable each one is useless without the other. When you create GISDK applications, you create your own UI Databases. When you run an addin or custom application, you are bining the platform with your own UI Database. You choose the UI Database you want to use when you install an addin or custom application, or by modifying the mand line that starts the platform. Compiling Resources When you write GISDK programs, they are stored in ordinary text files that are known as resource files. Resource files always have an extension of .RSC. Because Caliper Script is a piled language, the programs you write must be piled before they can be run. The program that piles the resources is known as the resource piler. The piled resources are stored in a UI Database. Here is a flow chart that shows the relationship between resources, the resource piler, the UI Database, and the platform. The resource piler can pile a single resource file, or a group of files, at one time. To pile a group of files, you create a list file. A list file is a text file with an extension of .LST that contains the names of all the resource files in your GISDK application, one per line. The resource piler checks resource files as they are piled for various types of errors, including errors in syntax, invalid statements, and mismatched doend statements. If errors are detected, the resource piler creates an error file listing each error and the line number at which it was detected. The error file has the same name as the resource file and an extension of .ERR, and is always placed in the same folder as the resource file itself. 5 GISDK includes several versions of the resource piler. You can choose to pile resource files using: ?? The buttons in the GISDK toolbox ?? The program from DOS or Windows ?? LoadResourceFile() from within your own GISDK application For more information, see... Compiling and Testing with the GISDK Toolbox Compiling with the StandAlone Resource Compiler Compiling with LoadResourceFile() UserDefined Compilation Flags Compiling and Testing with the GISDK Toolbox The GISDK toolbox is an addin that contains tools you use to pile and test GISDK applications: Tool Function Compile resource file(s) to the default UI Database Test a macro or dialog box Compile resource file(s) to a standalone UI Database Start the GISDK Debugger Execute one or more Caliper Script statements immediately When you installed TransCAD, the GISDK Toolbox addin was added to the file, just like any other addin. The button in the GISDK Toolbox piles resources into a UI Database named TEST_UI. When you pile a resource file (or several resource files in a list file) using the button, first the TEST_UI database is cleared, and then the piled resources are added to that database. The button in the GISDK Toolbox tests a resource that you piled into the TEST_UI database. You specify the name of the resource to run, and whether it is a macro or a dialog box. The button in the GISDK Toolbox lets you choose the UI Database in which to store the piled resources. The database you choose is cleared, and then the piled resources are added to the database. The button in the GISDK Toolbox starts the GISDK Debugger, which helps you find and fix runtime problems in GISDK macros. You can set breakpoints in resource files, see the call stack, see the values of variables, and set up a watch list. The GISDK Debugger runs along side TransCAD, in a separate window. 6 The button in the GISDK Toolbox lets you type Caliper Script mands into a dialog box and have them executed immediately. This is often helpful when you are testing or debugging your GISDK programs. There are many cases where immediate execution of a statement is helpful. For example: Statement When to use it ShowMessage() To display debugging information (., ShowMessage(GetLayer()) to display the name of the current layer。s the debugging message... X ShowMessage(Finished with + ) rec = GetNextRecord(vw + |, , ) end endMacro If this resource is piled with the X pilation flag, the debugging message will be included in the piled resource, and the name of each state will be d