This document covers the following topics:
The folder structure of the Software AG Designer has changed as indicated in the following table:
| Old Folder Name | New Folder Name |
|---|---|
| <your-installation-directory>/eclipse/<version>/ | <your-installation-directory>/Designer/eclipse/ |
| <your-installation-directory>/eclipse/updates/ | <your-installation-directory>/Designer/updates/ |
NaturalONE now supports Internet Explorer 11. However, with the current version of NaturalONE, applications running in RTL (right-to-left) mode cannot be executed under Internet Explorer 11.
For a list of the currently supported web browsers, see Supported Browsers in the Installation documentation.
This section describes new features and enhancements in NaturalONE's basic functionality for Natural application development. It covers the following topics:
It is now possible to add task tags such as TODO or
FIXME to your source code. NaturalONE uses the task tags that are
used for the Java compiler. See
Working with
Tasks in Using NaturalONE.
In the Natural preferences (see Setting the Preferences in Using NaturalONE), the following new items are available for task tags:
Task Tags syntax element on the Source Editor > Syntax Coloring page.
Task Tags tab on the Parser page.
It is no longer possible to change the object name of a DDM with NaturalONE. This functionality has been removed because Natural Development Server for Windows, UNIX and OpenVMS does not support any combination of DDM long name and DDM object name. The object name is now generated automatically from the long name that you specify when creating a DDM.
Moreover, the object name for a new DDM is finally defined on the server. NaturalONE tries to anticipate the name, but this works only if all objects from the server library are also contained in the Natural project.
Note:
With Natural Development Server for mainframes, the object name is
irrelevant.
It is now possible to use the Natural profiler with the local Natural runtime of NaturalONE.
The Profile As command is no longer used to define the event types for which trace data is to be collected on the server. Instead, this can now be defined in the Natural preferences. In addition, it is now possible to reduce the number of events sent by the trace session. See Profiler in Setting the Preferences which is part of Using NaturalONE.
The Natural Navigator view is now supported as a regular feature of NaturalONE. Customer feedback on the former preview version has been implemented. However, not all feedback has been implemented yet. Therefore, a later version of NaturalONE may include changes. Any feedback from our customers is still greatly appreciated. See Using the Natural Navigator View in Using NaturalONE.
New features in this version are:
Default View
The Natural Navigator view is now a default view
of the NaturalONE perspective. This means, it is automatically shown each time
you reset the NaturalONE perspective.
View Menu
The view menu of the Natural Navigator view
(drop-down menu at the top right of the view) now contains the corresponding
menu commands for the toggle buttons that are shown in the local toolbar of the
Natural Navigator view.
Natural Filters
It is now possible to define Natural filters for the nodes of the
Natural Navigator view. See
Filtering
Natural Objects and Libraries in Using
NaturalONE.
Properties View
The Properties view now shows enhanced,
Natural-specific information for a node which is currently selected in the
Natural Navigator view. Such information is not shown when
working with the standard Navigator view of Eclipse. See
Quickly
Viewing the Properties in Using
NaturalONE.
More Commands
Many context menu commands which were missing in previous versions
can now be executed from the Natural Navigator view.
The new Details view is a default view of the NaturalONE perspective. It shows detailed information on the children of the project, library or folder that is currently selected in the Navigator view or in the Natural Navigator view. See Using the Details View in Using NaturalONE.
With NaturalONE Version 8.3.3, support for Arabic shaping is still provided as a preview version. There will be no support for this preview version. Any feedback from our customers on this new feature is greatly appreciated. Since support for Arabic shaping is still under development, a later version of NaturalONE may include substantial changes to this type of support. See Arabic Shaping in Using NaturalONE.
This section describes new features and enhancements in Natural for Ajax and Ajax Developer. It covers the following topics:
The ROWTABLEAREA3 control is used to bind a two-dimensional Natural array to a grid. This grid separates the data structure for the business data from the data structure for the rendering data.
With the NJX:REQUESTCONTEXT control, the Natural application can access context information regarding the request.
The TEXT control now
supports the new properties maxrows,
maxrowsprop,
maxrowlength and
maxrowlengthprop which can be used to limit the
number of rows and the length of the rows.
This type of support was already available with NaturalONE Version 8.3.2. Due to an early documentation deadline, this fact could not be announced in the Release Notes for version 8.3.2.
The GOOGLEMAP control now supports the Google Maps JavaScript API v3. An API key is not needed any more, but when used in production, an API key should be used.
This type of support was already available with NaturalONE Version 8.3.2. Due to an early documentation deadline, this fact could not be announced in the Release Notes for version 8.3.2.
The elements LEFT and TOP of the
NJX:XCIOPENPOPUP control
are now also supported for page pop-ups. These elements were previously only
supported for browser pop-ups.
It was not possible to introduce this feature without producing the
following incompatibility as compared with previous handling of page pop-ups:
In order to open a centered page pop-up, the elements LEFT and
TOP need to be set to -1. If LEFT and
TOP are set to 0, the page pop-up is opened in the upper left
corner of the browser output area.
Previous versions contained an inconsistency in the focus handling during flush events. When a flush event was specified for a FIELD and the user moved the focus away from that FIELD, the following happened while the flush method was executed:
If alwaysflush="false" (default) was defined for the
FIELD, the Natural system variable *CURS-FIELD
contained the value of the Natural system function POS for the
FIELD that lost the focus.
On the other hand, if alwaysflush="true" was defined for
the FIELD, the Natural system variable *CURS-FIELD
contained the value of the Natural system function POS for the
FIELD that received the focus.
This inconsistency has been removed. Now when the user moves the focus
away from one input control to another,
*CURS-FIELD contains during the flush event the
POS value of the input control that received the focus.
This allows an application to identify both the input control that lost the
focus (by means of the flush event) and the input control that received the
focus (by means of *CURS-FIELD).
Note:
If an application relies on *CURS-FIELD
containing the POS value of the input control that lost
the focus, it can achieve this behavior by setting the parameter
flushreceivespreviousfocused="true" in the configuration file
cisconfig.xml.
A new section, The Development Lifecycle: Step by Step, is available in the NaturalONE in a Nutshell documentation. It summarizes the required steps for the preferred development scenario.
The Lifecycle Manager is no longer offered for installation. The Lifecycle Manager documentation has been removed from the documentation set for NaturalONE Version 8.3.3. Please continue to use your existing installation which runs with CentraSite Version 8.2.
