Tour of the IDE
Go Up to Getting Started with Appmethod
When you start Appmethod, the integrated development environment (IDE) launches and displays several tools and menus. The IDE helps you visually design user interfaces, set object properties, write code, and view and manage your application in various ways.
This help topic describes the tools that are available in the IDE. Please note that the specific tools that are available to you vary depending on the edition of Appmethod you are using.
- 1 Welcome Page
- 2 Accessibility Options
- 3 Desktop Layouts and Autosave Project desktop
- 4 Working with a Form
- 5 Form Designer
- 6 Tool Palette
- 7 Object Inspector
- 8 Object Repository
- 9 Project Manager
- 10 Data Explorer
- 11 Structure View
- 12 History Manager
- 13 Code Editor
- 14 Debugger
- 15 File Browser
- 16 See Also
When you open Appmethod, the Welcome Page appears with a number of links to developer resources, such as product-related articles, training, and online Help. As you develop projects, you can quickly access them from the list of recent projects at the top of the page. If you close the Welcome Page, you can reopen it by choosing View > Welcome Page.
Working with IDE, you can use MS Active Accessibility (MSAA) tools. You can activate Windows accessibility tools from the Start Menu via All Programs > Accessories > Accessibility.
Desktop Layouts and Autosave Project desktop
The default IDE desktop layout includes some of the most commonly used tools. You can use the View menu to display or hide certain tools. You can also customize your desktop by moving or deleting elements, and you can save the desktop layouts that work best for you.
Desktop settings are saved in a
.dsk file, and the Autosave Project desktop option (on Tools > Options > Environment Options) enables the saving of a
.dsk file for the current project. The
.dsk file also preserves the current breakpoint settings and watches. The
<myproject>.dsk file is saved inside your project folder. See Saving Desktop Layouts.
Working with a Form
Typically, a form represents a window in the user interface that you are designing. At design-time, a form is displayed on the Designer surface. You add components from the Tool Palette to the form to create your user interface.
Appmethod provides a rich library of forms, as described in the following section. Select the form that best suits your application design, whether it is a Web application that provides business logic functionality over the Web, or a Windows application that provides processing and high-performance content display. To switch between the Designer and Code Editor, click their associated tabs below the IDE.
To access forms, choose File > New > Other.
The Form Designer, or Designer, is displayed automatically in the center pane when you are using a form. The appearance and functionality of the Designer depends on the type of form you are using. To access the Designer, click the Design tab at the bottom of the IDE.
Visual components appear on the form at design-time and are visible to the end user at run time. They include such things as buttons, labels, toolbars, and listboxes.
If you are creating components for a form, you can register an object type and then indicate various points on or near a component's bounds that are "alignment" points. These "alignment" points are vertical or horizontal lines that cut across a visual control's bounds.
When you have the alignment points in place, you can supply UI guideline information so that each component adheres to rules such as distance between controls, shortcuts, focus labels, tab order, maximum number of items (listboxes, menus), and so on. In this way, the Form Designer can assist the Code Developer in adhering to established UI guidelines.
If the Snap to Grid option is enabled (on Tools > Options > Environment Options > Form Designer), and Use Designer Guidelines is also enabled, the designer guidelines take precedence. This means that if a grid point is within the tolerance of the new location and a guideline is also within that distance away, then the control snaps to the guideline instead of the grid position, even if the guideline does not fall on the grid position. The snap tolerance is determined by the grid size. Even if the Snap to Grid and Show Grid options are disabled, the Designer still uses the grid size in determining the tolerance.
The Tool Palette, located on the right-hand column, contains items to help you develop your application. The items displayed depend on the current view. For example, if you are viewing a form on the Designer, the Tool Palette displays components that are appropriate for that form. You can double-click a control to add it to your form. You can also drag it to a desired position on the form. If you are viewing code in the Code Editor, the Tool Palette displays code segments that you can add to your application.
In addition to the components that are installed with Appmethod, you can add customized or third party components to the Tool Palette and save them in their own category.
You can create templates that are made up of one or more components. After arranging components on a form, setting their properties, and writing code for them, you can save them as a component template. Later, by selecting the template from the Tool Palette, you can place the preconfigured components on a form in a single step; all associated properties and event-handling code are added to your project at the same time. You can reposition the components independently, reset their properties, and create or modify event handlers for them just as if you had placed each component in a separate operation.
The Object Inspector, located on the left, lets you set design time properties and create event handlers for components. This provides the connection between visual appearance of your applications and the code that makes the application run. The Object Inspector contains two tabs: Properties and Events.
Use the Properties tab to change physical attributes of your components. Depending on your selection, some category options let you enter values in a text box while others require you to select values from a drop-down box. For Boolean operations, you toggle between True or False. After you change physical attributes of your components, you create event handlers that manage the components.
Use the Events tab to specify the events for a specific object you select. If there is an existing event handler, use the drop-down box to select it. By default, some options in the Object Inspector are collapsed. To expand the options, click the plus sign (+) next to the category.
Certain nonvisual components, for example, the Borland Data Providers, allow quick access to editors such as the Connection Editor and Command Text Editor. You can access these editors in the Designer Verb area at the bottom of the Object Inspector. To open the editors, place your cursor over the name of the editor until your cursor changes into a hand and the editor turns into a link. Alternatively, you can right-click the nonvisual component, scroll down to its associated editor and select it. Note that not all nonvisual components have associated editors. In addition to editors, this area can also display hyperlinks to show custom component editors, launch a web page, and show dialog boxes.
To simplify development, Appmethod offers pre-designed templates, forms, and other items that you can access and use in your application.
Inside the Object Repository
The Object Repository contains items that address the types of applications you can develop. It contains templates, forms, and many other items. You can create projects such as class library, control library, console applications, and many others by accessing the available templates.
To open the Object Repository, choose File > New > Other. A New Items dialog box appears, displaying the contents of the Object Repository. You can also edit or remove existing objects from the Object Repository by right-clicking the Object Repository to view your editing options.
Object Repository Templates
You can add your own objects to the Object Repository as templates to reuse or share with other developers. Reusing objects lets you build families of applications with common user interfaces and functionality to reduce development time and improve quality.
You can add a starter project, demo, template, or other useful file to the Object Repository and then make it available through the New menu. Choose Project > Add to Repository. Select your file. Now when you select the File > New command, you can choose the file you just added and work with a new copy of it.
Appmethod allows you to create multiple custom template libraries to use as the basis for creating future projects. Template libraries let you to declare how projects can look, and they enable you to add new types of projects to the Object Repository.
A project is made up of several application files. The Project Manager, located in the top right-hand column, lets you view and organize your project files such as forms, executables, assemblies, objects, and library files. In the Project Manager, you can add, remove, and rename files by using the toolbar buttons or the context menu. You can even invoke the Project Options dialog box from the context menu on the Project Manager.
You can combine related projects to form a project group. You do this by right-clicking the default project group node () in the Project Manager and selecting either Add New Project or Add Existing Project. Linking several projects into one project group enables you to compile the entire project group at one time. But you can also compile any single project by right-clicking a project node and selecting one of the compile or build commands on the context menu.
After you deliberately create a project group, you are prompted to save the
.groupproj file when you exit the IDE or enter a save command for any of the included projects. You can also explicitly save a project group using the context menu commands.
The Data Explorer lets you browse database server-specific schema objects, including tables, fields, stored procedure definitions, triggers, and indexes. Using the context menus, you can create and manage database connections. You can also drag and drop data from a data source to most forms to build your database application quickly.
The Structure View shows the hierarchy of source code displayed in the Code Editor, or components displayed on the Designer. When displaying the structure of source code, you can double-click an item to jump to its declaration or location in the Code Editor. When displaying components, you can double-click a component to select it on the form.
If your code contains syntax errors, they are displayed in the Errors folder in the Structure View. You can double-click an error to locate its source in the Code Editor.
You can control the content and appearance of the Structure View by choosing Tools > Options > Environment Options > Explorer and changing the settings.
The History Manager, located in the center pane, lets you see and compare versions of a file, including multiple backup versions, saved local changes, and the buffer of unsaved changes for the active file. If the current file is under version control, all types of revisions are available in the History Manager.
The Subversion Integration in the IDE is implemented on the History Manager, which displays Subversion information whenever Subversion information is available from the file system.
The History Manager is displayed to the right of the Code tab and contains the following tabbed pages:
- The Contents page displays current and previous versions of the file.
- The Diff page displays differences between selected versions of the file.
- The Info page displays all labels and comments for the active file.
You can use the History Manager toolbar to refresh revision information, revert a selected version to the most current version, and synchronize scrolling between the source viewers in the Contents or Diff pages and the Code Editor and for window navigation (such as Go to next diff).
The Code Editor, located in the center pane, provides a convenient way to view and modify your source code. It is a full-featured, customizable, UTF8 editor that provides refactoring, automatic backups, Code Insight, syntax highlighting, multiple undo capability, context-sensitive Help, Live Templates, Smart Block Completion, Find Class, Find Unit/Import Namespace, and more.
The integrated debuggers let you find and fix both runtime errors and logic errors in your Appmethod application. Using the debuggers, you can step through code, set breakpoints and watches, and inspect and modify program values. As you debug your application, the debug windows are available to help you manage the debug session and provide information about the state of your application.
You can perform basic file operations using the File Browser, a dockable Windows style browser pane. Open the File Browser to search, rename, or perform source control operations on a file.
To perform an operation on a file, choose View > File Browser, browse to the file, right-click the file, and select the operation to perform.