You are hereChanges in Aria 4.0

Changes in Aria 4.0


By luano - Posted on 29 December 2008

The table below lists the changes and enhancements made in Aria 4.0. The table will be updated until the final release of Aria 4.0 is made public.

Reference Description
2005998 Remove AttribitedComponent interface

The components now set their properties as normal Java beans using properties. The AttributedComponent interface is completely removed.
2017683 Support Commons validators

Support for commons validators and/or other validation systems is added. The validations should work on a field by field or per class basis. Commons validations are added as a separate project.
2017690 Extended Popups
Pojo support added for popups in the form on PojoDialog
2017694 Error Badges
Extends the error badges to common components. Works for edits and labels but overlays the component whereas as it would preferrably draw outside thee bounds of the widget. Support works for compound components like drop downs where the badge would have initially painted but then
disappears.
2017695 Error tooltip support
Allow tooltips (and/or error badges) to display an error message. Once the error is cleared the original tooltip should be restored.
2017712 MetroBank: Popluate database with dummy/sample data
Provide a script for setting up a new database and populating it with sample data
2021305 Refactor the registry and component adapter interfaces

Refactor the registry and component adapter interfaces to reflect the removal of the AttributedComponent interface. The component should now only
use the bean properties either through the beaninspector or via reflection. This should simplify the setup considerably.
2021306 Refactor the builder classes
Examine the builder classes to see if they could be simplified in light of the removal of the componentAttribute interface. A single method of setting properties is now in place and should remove the need for some code.
2028625 Document the build process

For the runtime and the editor plugins. See the wiki on SourceForge and the PDF documentation.
2092664 MetroBank: Remove unused jars
Remove the jar references from the web project
2146170
Allow pojopanel to dynamically bind. The class is therefore retrieved from the object passed to the PojoPanel and the panel is configured appropriately
2148985 Update style selectors
Update the style selectors to choose the class name in a CSS manner. Mostly this releated to fixing a bug in the StyleManager. Styles can now be set according to the components's simple class name.
2148987 Add Generic PojoDialog class
Add Generic PojoDialog class to save repeating the definitions for each dialog, plus helper methods. New class added and used in metrobank example.
2157273 Integrate styles and UI manager
Integrate styles and UI manager allowing styles to opt in ot out, and map styles to ui manager keys
2176474 Demo pojo views
Add view customization to the metroBank example for dialog, tables and panels to the MetroBank example
2183778 Sync component factories
Change the page helper to use the same component factory as the builder
2187358 Automatically load view file
Load view file using a naming convention to locate the view file for the PojoPanels, see the MetroBank example for an sample.
2187619 Put metroBank SOAS on background threasd
The initial db load delays display of the UI, so the Spring remote object access is placed on a background thread and the login blocked till the objects are available.s
2188728 Generate DTOs for nested objects
Complement the flattening of DTOs with a nested DTOs facility, whereby the referenced objects are also fetched - a deep copy.
2282333 Guide editor bk color too light
The guides background was not distinguishable from the page on some LCD monitors, so the colour was changed.
2282341 Anti alias guides
They are a bit jagged within the editor
2308358 Only show component tabs for libraries found
Ìn the editor, only show component tabs for libraries found instead of showing blank tabs
2332888 Remove open in framesets option
It's confusing, error prone and complicates the editor. Editing a page within a frameset is of marginal value ass that page could be used in many places and circumstances. Furthermore, the frameset is reused and the content shown at runtime might not match the design time frameset.
2363817 Change Page class to interface
Change Page class to interface and provide Swing, AWT specific implementations, this allows the component hierarchies to be separated and also allows more widget set specific behavior.
2472948 Use symbolic constants for guides
rel and abs can now be used instead of the values 0, 1, 2, 4 for the guide positioning and coordinate types.
2472949 Display guides at runtime

Set startup properties DrawGuides=true for the debug runtime to display the guides
2475273 Set the new component name
Set the new component name when adding a new component. The layer manager uses the component name to check for the background layer. Other components make similar/specific use of the component name. This change requires modification of the component factory APIs and may have knock on effects for anyone calling the component factory directly.
2017699 OSGi support
Basic OSGi support is added via the maven build. The runtime packages are exported as an OSGi bundle. Later further OSGi support will be added.