Take a look onto the lightweight Pivot component, that was functionally enriched with the last update.

The usage is very simple: you pass the raw data (some key-value-tupels), define which keys to arrange on the left and which keys to arrange on the top – that’s it!

In addition you now can interact with the component in a fine-granular way and…

• update the rendering (colors, formats, widths, …)
• receive events from user selections so that you know what’s going on inside

The component is part of the add-on package which is available for free – including all source code.

A new add-on is available: the “Cluster and Version Manager”.

The add-on addresses two functional areas:

• Load distribution – How to distribute load in a cluster of multiple CaptainCasa runtime installations
• Version management – How to set up scenarios in which different versions of one application run in parallel and how to seamlessly migrate users from the one to the next version

The Cluster and Version Manager is an add-on. Which means: you receive both the runtime version (.war file) and the code (GIT repository) and you are allowed to do anything with it! There is no cost or whatever involved for using it.

The Cluster Manager is not a replacement of other frameworks in the area of cluster management (Docker, Kubernetes, Spring Boot, …) – but works in harmony with these frameworks!

Please check the documentation >HERE<.
 

During application processing by default some animated waiting-image is shown on top of the current dialog:

Now it is extremely simple to notify the user in addition about the progress of the server side processing and to pass some progress level and text to the client:

There is no necessity anymore to decouple the application processing into some own thread in order to “free up” the UI-request-thread. You just need to call a new Java-API:

...
BlockerInfo.sendProgressToClient(<text>,<percentageNumber>);
...

Internally the progress information is passed through a web socket connection that is automatically established between the client and the server.

Dear community,

we will not allow this year to pass by without having met as community! Too many things have happened inside our framework that require to be communicated – and too many things have happened on your side to be communicated back to us.

So we decided to close this year with an online version of the community meeting. The meeting is split up into 3 sessions, each one lasting 1 hour. The sessions start at:

• Thursday, Dec 3rd, 15:00h (German time)
• Thursday, Dec 10th, 15:00h
• Thursday, Dec 17th, 15:00h

Please check and save the dates. All logistics details are available in the forum: please click >HERE<.

Meeting you “online” will not be the same experience as our normal, “real” meeting! (And there is no evening event the day before…) But: let’s give a try! We are looking forward to meeting you!

Björn + Team

We want to (re-)emphasize this way of implementing your server-side view part. So we wrote some tech paper, showing how to use and how to take benefit. Please take a look directly HERE or open the document in our documentation area.

There are several updates within the grid processing (component FIXGRID) that are part of the recent updates.

The grid rows’ heights now can follow the height of the contained cell components – so that each content row receives the individual size that is desires to be correctly displayed:

Still the normal grid features (server side scrolling, moving data through components rather than building up a big number of components) are kept.

You now can group columns into groups of columns – and build up any grouping hierarchy level within the column headers:

Sorting, re-arranging of columns by drag/drop, hiding/showing and resizing of columns is still supported – and was adapted correspondingly. Example: you only can re-arrange columns within one group.

Please check the demo workplace (“News” section) for examples and detailed information about how to use.

Up to now the Maven repository holding CaptainCasa artifacts was located at https://www.CaptainCasaDemo.com/mavenrepository.

We now provide a new address which is https://www.CaptainCasa.com/mavenrepository – so that the Maven repository is not part of our demo environment anymore.

The new Maven repository contains all CaptainCasa versions from January 2020 on.

Please update your Maven build scripts. Until end of this year we will upload updated artifacts to both repositories. From begin of 2021 on we will only upload to the new repository anymore.

Our partner Evolution IT in Sofia, BG, is providing development services for CaptainCasa-based applications – including the development of screen testing environments. Based on the practical experience gained in a couple of projects, Evolution IT developed a screen testing framework which internally is based on Selenium and which adds administration functions on top, e.g.: definition of test cases, management of result, notification on errors.

Please take a look into this “video from the labs”:

Interested? – Contact us (info@CaptainCasa.com)!

We are carefully updating our default styling and now did apply it to the online demo workplace.

You may open the demo workplace >HERE<.

Updates include:

• Darker colors in general
• Fields are shown as underlined areas – without explicit box around

•  In the demos themselves we step by step use fields with floating labels – instead of the typical label-field-combination

Of course all existing styles are still supported and still valid. And of course it is your decision if you want to follow these changes with your own style. – So: please take a look. Your feedback is appreciated!

All field components now support the direct definition of a so called floating label. The label text is drawn as gray background text if the field content is empty:

When the user or the application defines some value for the field then the label text moves up to the left top corner of the field:

In addition there is a new container (name “labelcontainer”) which allows to draw the exact same arrangement around other components, e.g. check-boxes or radio-buttons, so that these components are embedded into the same type of look and feel: