With the release of version 5.2 of the Agentry Mobile
Platform, additions have been made to the Eclipse preference pages
by the Agentry Editor plug-in. These preferences affect the behavior
of the Editor as a whole, or the appearance and behavior of the
various views within the Agentry Perspective.
The following sections detail each of these new preference pages.
To access these pages, select the menu item Window | Preferences in
Eclipse. In the Preference screen, select the Agentry root
node on the left side of the screen.
Compare Preferences
The Compare Preferences
page displays the preferences for the Comparison View’s appearance.
the settings provided allow for the personalization of the colors
used to denote the definitions when in different states within this
view. There is also a preference for the number of previous revisions
to display when the local project is connected to a share repository.
For
each of the color preferences, the foreground and background color
can be set by selecting the desired color from a color palette.
The foreground color setting specifies the text color and the background color
specifies the field behind the item. The following is a list of
each of these preferences:
- Selected Definitions: This
preference specifies the color scheme for the currently selected definition
in the Comparison View.
- Matching Definitions: This preference specifies the color
scheme for definitions when the two definitions match exactly in
both projects being compared in the Comparison View.
- Non-Matching Definitions: This preference specifies the
color scheme for definitions that do not match between the two projects
being compared in the Comparison View.
- Non-Matching (Unimportant) Definitions: This preference
specifies the color scheme for definitions that do not match between
the two projects being compared in the Comparison View when the
difference between the two is an unimportant difference, such as
a difference in the descriptions of each.
- Source-Only and Editor-Only Definitions: This preference
specifies the color scheme for definitions that exist in only one
of the projects being compared in the Comparison View.
- External Compare Tool: This preference allows for the
selection of the external comparison tool used to compare two text
files from the Comparison View. By default the tool Windiff is used. However,
another tool can be used provided it can accept two arguments, each
representing the files to be compared. This preference should be
set to the full path and file name of the executable file of the
comparison tool.
Compression Settings
The Compression Settings
page displays the preference settings for compressing Agentry definition
files during export, export differences, and publish operations.
The default is to compress the definition files generated during
these operations.
- Compress Export: This preference,
when selected, results in the creation of compressed export files
when the Agentry application project is exported. The file extension
for the export file is set to .agxz. If the file
is not compressed the resulting export file has a file extension
of .agx.
- Compress Export Differences: This preference, when selected,
results in the creation of compressed export files when the Agentry
application project is exported via an Export Differences operation.
The file extension for the export file is set to .agxz.
If the file is not compressed the resulting export file has a file
extension of .agx.
- Compress Publishes: This preference, when selected, results
in the published definitions, stored on the Agentry
Server,
being compressed. The Server recognizes this compression and automatically
decompresses it when loading the definitions. if this option is
not selected, definitions are not compressed when published to the
Server and the Server will recognize this as well. No change is
needed on the Agentry
Server to
reflect the compression setting for publish.
New Definitions
The New Definitions preference
page contains preferences related to the creation of new definitions within
the application project. This includes setting reminders on definitions,
default names for certain definition types, and the default selected
data type for complex table fields. These settings only specify default
values initially selected and all values can be changed when actually
creating the definitions referenced here. The following list describes
each of the preferences found on this page:
- New Definition
Reminders: Each definition type within the project supports
reminders, or text values displayed as informational messages in
the Problems View. By default reminders are set manually by the
developer. Using this preference setting it is possible to set a
default reminder message for all new definitions created in the
project, including a default reminder message.
- Transaction Naming: The default name of all new transactions
can be specified to be either Noun-Verb (default) or Verb-Noun.
Regardless of the default set here, names can always be changed
when adding a new transaction definition.
- Rule Naming: The default name of all new rule definitions
can be specified to be either Name-Usage (default) or Usage-Name.
Usage refers to the attribute type referencing the rule, e.g. Enable
Rule, Initial Value Rule, etc. Regardless of the default set here,
names can always be changed when adding a new rule definition.
- Complex Table Field Type: This preference allows you
to specify the default data type selected when creating a new complex
table field definition. This is only the default selection when a
new field is first created and can be changed during the creation
process to a different data type if needed.
Perspectives
This section specifies the
behavior of Eclipse related to the Agentry perspectives when opening
an Agentry application project when there is no Agentry perspective
currently open. These preferences specify whether to always open
an Agentry perspective, never open one, or to prompt you to choose whether
or not to open the perspective. Included in these preferences is
a list of the available Agentry perspectives where the specific
one to open by default is selected.
Project Explorer
The Project Explorer
preferences page contains the preferences that affect the appearance
and behavior of the Project Explorer View, as well as the Properties
View interaction with it. The following list describes each of the
preferences found on this page:
- Link Properties View breadcrumb
navigations with the Project Explorer View: When this preference
is set to true, navigating in the Properties View using the navigation
buttons for back and forward will automatically select the definitions
in the Project Explorer View.
- Link Properties View parent navigations with the Project
Explorer View: When this preference is set to true, using the
parent arrow in the Properties View to navigate to the parent or
ancestor definition of the one currently displayed will automatically
select that definition in the Project Explorer.
- Link Properties View hyperlink navigations with the Project
Explorer View: When this preference is set to true, clicking
a hyperlink label in the Properties View to display the referenced
definition will automatically select that definition in the Project
Explorer View.
- Link Trash Bin definition restores with the Project Explorer
View: When this preference is set to true, the restoration of
a definition from the Trash Bin View will automatically select that
definition in the Project Explorer View.
- Link Visual Screen Editor selections with the Project Explorer
View: When this preference is set to true, the selection of
a screen control (detail screen field, list column, button, etc.)
in the Layout View of a screen definition will result in that same
definition being selected in the Project Explorer View.
- Sort Order: This preference specifies how the definition
type nodes in the Project Explorer View should be sorted. The options
are Traditional, which sorts the type nodes as in releases of Agentry prior
to 5.2; and Ascending, which sorts the type nodes in alphabetical
order.
Tagging Configuration
The Tagging Configuration
preferences page contains the preferences for the definition tagging
behavior of the project. It is also possible to add new tags to
the project within this preference page. Note the preferences on
this page are specific to the currently open Agentry application
project. The following list describes the preferences displayed
on this page:
- Show tags bar in the Properties View: This
option shows or hides the tags bar in the Properties View. If the
current open Agentry application project is connected to a share,
this preference is always true and cannot be changed.
- Auto-Tagging (Public): Within this section each of the
public tags for the project are listed, represented as a button.
One or more of these buttons can be selected to specify that tag
should be applied to any definition changed, added, or deleted in
the current project. Clicking the tag configuration button within
this section will display the tags dialog where additional tags
can be added to the project.
Team Configuration
The Team Configuration
preference page contains preferences for the team configuration
behavior. These preferences are specific to each Agentry application
project. These preferences are not available when the current project
is not connected to a share. The following list describes these
preferences:
- Auto-Tagging (Private): Private auto-tagging
describes the behavior where the Editor automatically applies a
private tag to any definition when it is modified, added, or deleted
in the current project. This tag is used in comparisons with the
share revisions, and is also displayed in certain operations to
allow for the selection of definitions with this tag. The preference
setting on the Team Configuration preference page allows for a customized
value to be used as the name of this tag. By default, if this preference
is blank, the developer’s Windows user ID is the tag name.
- External File Handling: This preference specifies whether
it should be required that the Agentry Development Server is
specified before any share operations are executed that involve definitions
with an external script normally stored on the Development Server.
As examples, when this preference is true, a new project cannot
be imported from a share without specifying the Development Server
for the new project; a SQL step cannot be updated from the share
unless the Development Server has been specified.
- Share Revisions Menu Count: This preference specifies
the maximum number of revisions to display at one time in the revision
menu of the Comparison View. This preference setting only affects
the Comparison View’s behavior when the open Agentry application
project is connected to a share repository.