This topic outlines the capabilities that are new in version
8.5.1.
Rich UI
By default, the following
Rich UI system projects are in use:
- For EGL widgets that are not based on Dojo: com.ibm.egl.rui_4.0.1.1
- For EGL Dojo widgets: com.ibm.egl.rui.dojo.widgets_2.1.0.1
- For EGL Dojo samples: com.ibm.egl.rui.dojo.samples_2.1.0.1
- For the local Dojo runtime access: com.ibm.egl.rui.dojo.runtime.local_1.6.1
The following projects support use of Content Delivery
Network (CDN) for Dojo 1.6.1:
- Google Dojo runtime access: com.ibm.egl.rui.dojo.runtime.google_1.6.1
- AOL Dojo runtime access: com.ibm.egl.rui.dojo.runtime.aol_1.6.0
Setup details are available:
- For instructions on importing the Rich UI system projects, see Importing product-supplied projects.
- If you are upgrading to a new Dojo runtime project from one of
your existing Rich UI projects, you must upgrade the EGL build path
in your project. For details, see the section named "Outline of widget-upgrade
tasks" here: Overview of EGL Rich UI.
Here are new capabilities:
- If you are concerned about memory leaks, you can use the UtilLib.destroyRUIHandler function
to request removal of the widgets in a handler, in any handlers embedded
in that handler, and in any handlers embedded in the embedded handlers,
to any level of depth. For details, see Rich UI memory management.
Version 8.5.1 does not support Rich UI development on
a 64-bit Linux platform. Restrictions
in external software prevent that support, for now.
Java processing
Native
and generated Java™ code can
now share database connections, allowing you to commit database changes
that were made earlier in a run unit, even though the run unit contains
both kinds of code. For details, see SharedResourcePowerServer and JavaLib.getSharedResourcePowerServer.
Also,
you can now specify the character encoding used during access of a
file that is related to an EGL CSV record. The technique involves
setting the conversionTable property when you create a resource
association. For details, see Association elements.
For an overview of support for CSV records, see CSVRecord stereotype.
Setting new preferences for the EGL Debugger
Two
new preferences are available when you click and then expand
EGL and
click
Debug:
- Avoid stopping in a part if its source code is unavailable
(automatically step through)
Specify how the debugger
will respond if it accesses a part in an EGLAR file, if the source
code is unavailable.
- Avoid a prompt for same-named programs by accessing
the first one found in the EGL build path
Specify how
the debugger will respond if it accesses a program when duplicate
same-named programs are in your EGL build path or workspace.
For details, see Setting preferences for the EGL debugger.
Saving processing time during an automatic
build and generation
You might invoke an Ant script to clean
a workspace and cause an automatic build and generation. In that case,
you can use a Java VM argument
named egl.build.gen.debug to specify whether the generated
output includes debugging information. The default for the argument
value is true, but you might set the value to false if
you want to save processing time.
For details, see Generating with an Ant script.