![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
File > New > New View (Apex/Summit)Use File > New > New View to create a new view. The command displays the New View dialog box.
Command Line Interface: create_working, create_release
New View Dialog Box Fields:
Name Field
Enter the name of the view you wish to create
Subsystem Field
Subsystem specifies the containing subsystem or a non-view directory in a subsystem. Otherwise, a view will not be created.
View Options
The options for the new view are organized under the following tabs:
- Options Tab
Required options including view type, language, architecture, model, imports and storage directory.
- Other Tab
Access control, associated group and interface only.
- RCI Tab (Ada only)
- Shadow Tab
By default, the Options tab is displayed. Click on one of the other tabs to access the options and fields associated with it.
Options Tab
View Type
The View Type pull down menu provides two options:
- Working Option
Provides an area in a subsystem where individual developers can do day-to-day work and integrate changes.
- Release Option
Provides an area in which the changes from multiple developers can be integrated and imposes restrictions on some operations. You can execute all import, export, and compilation operations. You can execute all version-control operations in a development release except for the Control > Check Out (Apex/Summit), Control > Check In (Apex/Summit), and Control > Abandon (Apex/Summit), commands or any command that implies these operations.
Model Selection
There are often many models to choose from when creating a new view. The Model Selection section of this dialog is designed to assist you in narrowing down the number of models you have to choose from.
- Native or Cross Radio Box
This radio box is visible only if cross has been enabled. If it is not visible, you are limited to native models and views.
Select Cross to create an embedded view, Rational Exec, Tornado, or LynxOS.
Select the model field's Navigator Icon for help choosing a cross model.
Select Native to create a native view. The Language and Host Architecture pull down menus are displayed.
- Language Pull Down Menu
The Language pull down menu provides the following options:
The Language Type is defaulted based on the setting of APEX_DEFAULT_MODEL.
- Host Architecture Pull Down Menu
The Host Architecture pull down menu provides options corresponding to the architectures supported by Apex (for example, sun4_solaris2, hppa_hpux, etc.).
The host architecture is defaulted based on the setting of $APEX_ARCH.
Once you have set the above pull down menus to your desired values, click the Alternatives button to view the list of models that meet your criteria. If the settings of the pull down menus matches exactly one model, that model is automatically entered in the Model Field.
Model Field
In the Model field, enter the view name on which to base the new view. Subdirectories, switches, compiler options, and imports of the new view are copied from the model view. The current model appears in the Model field by default. To view additional models available for your configuration, use the Alternatives popup. A list of alternative models is displayed which is based on the values of view type, host architecture, and cross architecture (cross-only). In addition, the list includes the models listed in your Active Projects. Active projects are discussed under File > Setup.
If you are creating an RCI view, be sure to specify an RCI model here.
More information on models is provided in the Programmer's Guide.
Imports Field
Use the Import field to specify the imports of the new view. The view or configuration to be imported is added to any already specified by the model. You can name only one view or configuration.
Storage Check Boxes
Use the storage check boxes Storage field to specify a location for physical storage.
- Place storage in parent subsystem (the default)
The physical storage for the view is located within the storage area of the parent subsystem.
- Place storage in directory:
Clicking this check box requires that you provide a storage location in the supplied text field. When you use this field, symbolic links are created from the logical location to the physical location.
New View Check Boxes
- Visit the new view
When this check box is selected, the new view will be opened in a Directory Viewer window.
Other Tab
The following are displayed when the Other Tab is selected.
- Access Category
Use the Access Category button to specify access permissions for this view. If model is selected, permissions are taken from the model. Access control is described in the Concept's Guide
- Associated Group
Use this button to specify the group access to this view. Choices include all the groups the current user is a member of. If Inherit is selected, the group access of the enclosing directory is used. User is the effective group of the current user. Access control is described in the Concept's Guide
- Interface Only
Select the Interface Only option to create an interface view. Interface views contain only interface files, such as specifications and generic instances. Accepting changes from a non-interface view into an interface view moves interface units only. Select this button if you wish the view to be an interface view.
RCI Tab (Ada only)
The following options are displayed when the RCI tab is selected.
These options are used to specify a target Ada library (Target Directory) that corresponds to the specified host view. (Depending on your RCI customization, the elements of the Ada library required by your target compiler will be built, including the Ada program library and import information.)
If the Target Directory does not already exist on the target, it will be created and associated it with the selected host view. If the RCI Target Directory does exist on the target but is not an Ada library, it will be converted it into an Ada library before associating it with the host view. If the RCI Target Directory exists on the target and is already an Ada library, it will just be associated it with the selected view.
Note: Do not assign two views from the same subsystem to the same target library, unless your customization specifically requires this structure.
Once the target library has been created, all units in the host view are marked as requiring recoding on the target.
When you create a target library for a view that is imported by others, the importing views' imports are made obsolete.
Before you compile units in one of the importing views, you must refresh its imports (use Control > Maintenance > Refresh (Apex/Summit)).
Some buttons work in pairs, and in addition, button combinations are only allowed that create correctly formed RCI views. For example, a host-only view with or without a target library, or a host-target view with a target library.
Enable RCI Options Check Box
Indicates whether RCI options for new views are provided below.
Machine Button and Text Field
Use this field to specify which machine, if different from the host on which Apex is running, will perform target operations (such as library operations, compilation and linking) for this host view.
This field will be used to set the value of the RCI_COMPILATION_PLATFORM context switch for the host view.
Selecting the Machine button will cause the Compile on Host Only button to be deselected.
Compile on Host Only Button
No target compilations will occur for this view if this button is selected. Such a view can still have an associated target library which allows RCI views to be associated with precompiled target libraries.
Selecting the Compile on Host Only Button will cause the Machine Button to be deselected.
Target Directory specification fields:
These fields are used to specify a context, and a library name within this context, which will be combined (in a RCI customization specific way) to form the pathname for the target library to create and associate to the host view.
This pathname will be used to set the value of the RCI_TARGET_DIRECTORY context switch for the host view.
Context for target libraries Button and Text Field
The path to the directory context for the target library.
Selecting the Context for target libraries Button will cause the Target library context is default context Button to be deselected.
Target library context is default context Button
Sets target library context to a default value.
Selecting the Target library context is default context Button will cause the Context for target libraries Button to be deselected.
The value for the default context is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default context will be the host view's enclosing subsystem.
Target library name Button and Text Field
The name of the target library within the context.
Selecting the Target library name Button will cause the Target library name is automatically generated Button to be deselected.
Target library name is automatically generated Button
Sets target library name within the context to a default, automatically generated, value.
Selecting the Target library name is automatically generated Button to be deselected will cause the Target library name Button to be deselected.
The value for the default name is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default name will be targets/<view:t:r>.rci<view:e> (i.e. a subdirectory within a targets directory with the same base name as the host view, and extension .rciwrk or .rcirel, depending on the kind of the host view).
View has no target library Button
Views without target libraries must also be Host Only, although the reverse is not true as mentioned above.
Selecting this button will cause the Compile on Host Only Button to be selected, and the context and target library name Fields to become inactive.
Note: The creation of target libraries may or may not be implemented from one RCI customization to another. Also, your customizer can modify the way it operates (in particular the rules used to analyze and combine the provided target library context and name, and to generate default values for these).
For additional information, check the documentation for your RCI customization.
For additional detailed information on Apex shadowing, see the Client/Server Concepts Guide
Shadow Tab
The Shadow options are used with the Apex Shadowing product. The shadowing facilities of Apex provide support for linking Apex view to a working directory on a TCP/IP networked PC running Windows NT/95. Shadowing allows a view to be linked to a working directory on a PC where development, compilation, and testing can occur. Shadowing is integrated with Summit/CM allowing the files in the working directory to be controlled via Apex. With the addition of a PC X Server, the user can take advantage of the Apex GUI and custom dialogs which aid development and the use of shadowing.
- Enable Shadowing Options
This check box indicates whether shadowing options are to be specified for the new view. The shadow options will appear only if the APEX_SHADOW_ENABLED switch is set.
- Machine: - Name of the machine where the working directory resides.
- Port: - Port number on which the shadow server is listening for requests.
- Context: - Context to use for the working directory. The interpretation of this field is controlled by the USE_CONTEXT_AS_BASE switch.
For additional detailed information on Apex shadowing, see the Client/Server Concepts Guide .
Additional Topics
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |