|
Written by Administrator
|
|
Saturday, 08 December 2007 |
This release adds some new features especially for tables and enablement.
Tables now support deselect events and updating the table data yields more fine
grained events than the previous 'everything may have changed'. Furthermore, we
introduced a new TableRowsManager for updating more easily table rows
identifiable by primary key.
Enablement is about enabling view components according to some rules. Typical
examples are enabling a button when a table row is selected or enabling a button
when some validation was successful. Enablement is now supported within JCameo
by means of the WidgetEnabler class.
Topics for the next release will include a generalized layout mechanism and a
generator for generating Java classes from the view description, which will
allow to deploy a fully compiled JCameo application.
|
|
|
Written by Administrator
|
|
Thursday, 14 June 2007 |
|
The new version of JCameo has now a completely rewritten view component building process based on a schema description instead of the former Java Beans approach. After parsing the view description, the elements of the view component graph model are stored in eXtensible Data Objects (XDO), a light-weight variant of Service Data Objects.
This refactoring is an important step in direction of later tool support, like a GUI builder for JCameo. Furthermore, we improved the communication center by ensuring that every message will be delivered on the EDT, added a new widget CheckBoxMenuItem, and added a new property titlePainter for TitledPane. More minor additions are detailed in the changelog. |
|
|
Written by Administrator
|
|
Tuesday, 01 May 2007 |
|
The second JCameo release in 2007 has seen the light. Compared to earlier versions we have further increased the number of integrated widgets and improved the functionality of already existing widgets. So we have now a new busy label from SwingX, for indicating ongoing work, have integrated the filter features from SwingX for lists and tables, and support auto completion for text fields. Although the framework is at the moment quite stable, the current version introduces one incompatibility wrt earlier versions. While in earlier versions there was merely a single event for indicating a double-click on list resp. table rows (called row selected), we now distinguish between row selected (single mouse click) and row chosen (double mouse click). Please have a look into the changelog. |
|
|
|
<< Start < Prev 1 2 Next > End >>
|
| Results 1 - 4 of 6 |
