Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

> ## File menu enhancements

> Table 3–2 describes the new options on the File menu that support Progress Dynamics development.

> Table 3–2: Progress Dynamics-specific options on the File menu
> Menu | Description
> --- | ---
> Open Object | Runs the Open Object dialog box where you can choose a Repository-based object to open in the AppBuilder.
> Open Associated Procedure | If the currently selected object has a custom super procedure or data logic procedure associated with it, opens that procedure.
> Open File | Runs the Open File dialog box where you can specify a file system object to open in the AppBuilder. This is the same menu item as the Open menu item in the standard AppBuilder.
> Save As | Works as you would expect, except with dynamic containers. The correct way to save a dynamic container under a new name is to use the Container Builder to create a new container with the existing container as its template.
> Save Static Object As Dynamic | When you select an eligible static object, this option appears on the File menu and allows you to create a new dynamic object from the static object. You specify the Product Module and the option exists to include Repository Modules, modules of the framework. Note: If you have a StaticDataViewer (SDV) that contains a SmartDataField (SDF) and you want to save the SDV as a dynamic object, you must first register the SDF in the ICFDB Repository. If you register the SDF before you save the static viewer as a dynamic viewer, the SDF is referenced properly by the new dynamic viewer. However, if the SDF is not registered before you try to migrate the viewer from static to dynamic, you get an error message requesting that you register the SDF and the dynamic version of the viewer is not created.
> Save Dynamic Object As Static | When you select an eligible dynamic object, this option appears on the File menu and allows you to create a new static object from the dynamic object. This only applies to dynamic viewers and dynamic SDOs.
> Register in Repository | Displays the Register in Repository dialog box that you can use to add an AppBuilder-created file to the Repository as a static object.
> Re-Logon | Displays the Login window for you to login as a different user or with a different company.
> Session Reset | Displays the Session Reset window where you can specify to clear all client-side caching and restart session managers.

> ##### File New

> When you choose File New, the New dialog box appears, as shown in Figure 3–2.

> Figure 3–2: AppBuilder New dialog box

> Click the Template button to temporarily treat an AppBuilder procedure file as a template and place it in the objects list for the current AppBuilder session.

> The objects displayed for each Show filter type are determined by AppBuilder custom (`.cst`) files. See the "Object palette and object template information stored in the Repository" section for more details.

> ##### File Open Object

> The Open Object dialog box, shown in Figure 3–3, provides access to opening Repository objects for editing in the AppBuilder. It is limited to displaying only the object types described in the "Repository object types the AppBuilder edits" section.

> Figure 3–3: Open Object dialog box

> When you select an object in the browse and right-click, you have the option to:

> - Open the object.

> - Remove the object from the Repository.

> - View the property sheet for the object.

> ##### File Save Dynamic Object as Static

> This option invokes the default Save As dialog box, as shown in Figure 3–4, but is only enabled for dynamic objects. This means that it allows you to save a copy of a current dynamic object as a static object with a new name. You can also choose to register the new object in the Registry or choose deployment options for the object. Later sections in this chapter cover these topics.

> Figure 3–4: Save As dialog box

> ##### File Save Static Object as Dynamic

> On selecting the Save Static Object as Dynamic option, a dialog box opens, requiring you to specify the Product Module, as shown in Figure 3–5.

> Figure 3–5: Save As Dynamic Object dialog box

> You can also specify the name and particulars of a custom super procedure for the dynamic object.

> Notes: The object name defaults to the name of the static object, the only difference being the period between the name and extension is removed.
> The Product Module defaults to the last product module used when the last dynamic object was saved, but can be changed.
> The File Save menu item will behave normally; it will save an object as it is read in. Static = Static, Dynamic = Dynamic (same product module, same name). However, one exception is if a new untitled dynamic object is being saved, you will have the option of specifying the name and product module, as in the case of the Save as Dynamic Object option.

> ##### File Register in Repository

> To add the procedure to the Repository as a static object, open an existing static AppBuilder procedure and select File Register in Repository. The dialog box shown in Figure 3–6 appears.

> Figure 3–6: Register in Repository dialog box

> The check boxes at the bottom allow for marking the object for deployment. If any of the check boxes are selected, the object will be deployed to the specific destinations.

> After you complete the dialog box entries and choose OK, the framework adds the file to the Repository as a static object.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095