We added the MULTILABEL component – a text output component which is dedicated to output “masses” of text data. Typical use case: the output that is generated by reports.
The component’s status is “solid beta”. If you are interested in building up dialogs using this component, please contact us so that we can cooperate. We internally use the component in a new Page Bean Component for rendering simple pivot tables.
Please check the demo workplace for details.
We added the AVATARICON component, a special icon to render images or – if not available – initials of a person. Of course you can use it for any other purpose as well – and of course you can customize the look and feel in many aspects.
The RADIAL component renders some percentage value as graphics and as text.
You can define line size, color, font – and many other parameters.
We added a nice new page bean component “CCTimeLineVertical”. In the component you can arrange any other dialog content as item of a vertical time line:
The dialog content may be read-only content – but also may be interactive content.
Each content part is associated with some icon which is shown in the time line on the left. When the user clicks the icon, then the content part is collapsed and only some title is shown.
Up to now we delivered our documentation as PDF files. We now switched to HTML in order to simplify and accelerate access.
For better reading and for adequate printing each main chapter is represented as one HTML page. From the table of contents on the left you jump into the corresponding (sub-) headline inside the document.
The documentation can be viewed >HERE<.
Maybe some of you are interested in the way we create the HTML files: our documentation is written using Open Office Writer. While authoring we strictly keep to a few predefined format configurations (and do not do “free-style-formatting”). Due to the simple structure of the ODT-format (open document text) it is really simple to parse and convert content into HTML.
We updated the documentation about how to integrate the server-side processing with Spring – so that UI beans are directly loaded by a Spring context. You can download >HERE<.
In order to simplify the integration we in addition provide a library (“ccee_spring”) that either can be picked from the CaptainCasa download or that can be integrated by a Maven dependency. – And last but not least: there is a new Maven-project-archetype which includes the Spring integration in a pre-packaged way.
Please check the documentation for details.
We added some new demos to the demo workplace showing how layouts can flexibly adapt to their available screen space.
The component that is internally used is the ROWFLEXLINE component: it decides according to simple sizing rules if content components are arranged in one rows or if they are distributed to several rows. ROWFLEXLINE components can be nested – so that you have an outer ROWFLEXLINE component deciding about the “big blocks” and so that you use inner ROWFLEXLINE components to arrange the content within a block.
Please check the section “New Functions” inside the >Demo Workplace<.
The CaptainCasa tools now include a “Screen Map Editor” that allows you to better structure and access your layout definitions:
You can drag/drop layout definitions from the project and arrange them as boxes inside the map. From the box you can quickly navigate into the screen-related tools (e.g. Layout Editor). – You can create multiple maps for different areas of your application.
On the one hand the user selects an item within the grid – and wants to see detail data for the currently selected item. On the other hand loading detail data may be expensive on server side. Up to now you could differentiate between a “lightweight selection” (single click/touch, cursor navigation) and a “heavyweight selection” (double click/long touch, return key). But: the “heavyweight selection” required some explicit activity by the user.
We now introduced a nice alternative: the automated delayed selection. The user still can quickly navigate through the grid (e.g. by cursor up/down-keys), but: as soon as he/she stops with navigating for a certain duration, then a “heavyweight selection” is executed automatically, without requiring further user activity. As consequence it is made sure that the correct detail data is shown for a selected item, without executing the expensive loading of detail data with each step of navigation.
Please check the corresponding demo within the demo workplace (“New Functions”-area).
