...
The IProgress interface, used in all asynchronous tasks, has been replaced by the Progress implementation from to.etc.alg. The interface was completely useless as all async code created a specific implementation anyway, and the implementation was very limited in what it could do. The Progress implementation is fully threadsafe and allows nested accounting of progress.
Using enums as message bundle constants
Using BundleRef's with String constants for the message names is very deprecated and will be removed. The replacement is to use enum classes that implement the new interface IBundleCode interface. The enum values act as key names for the messages, and because an enum is a class the BundleRef is associated directly with the enum too. It makes it way easier to work with message bundles. See the localisation page for more details.
Rendering through a HTML template
For cases where you want to embed DomUI pages inside a complex existing HTML page you can now render DomUI pages through a HTML template. You set the template to use per page, for instance:
| Code Block |
|---|
getPage().setRenderTemplate(DomApplication.get().getResource("/mytemplate.html", ResourceDependencyList.NULL)); |
Inside the html template you need to place special constructs to indicate where DomUI can render its <head> and <body> information, by using:
| Code Block |
|---|
<% r.renderHeadContent(); %> |
and
| Code Block |
|---|
<% r.renderBody(); %> |
Metadata changes
Initialization of metadata
...