We applied 3D animations within the demo workplace so that starting/ ending and switching dialogs comes with a corresponding animation. Take a look.

…and tell us what you think about. We appreciate your feed back!

Take a look at demo Cube-rotations in our demo workplace:

The demo shows how a typical navigation scenario “filter-list-detail” can be upgraded by using 3D animations. We believe the upgrade is more than a “wow-effect” – but is a usage pattern, that the user will intuitively take over if consistently used within an application!

For developers: the component behind (“CUBEROTATOR)” is extremely simple to use and does not require any knowledge about transformations at all. All information behind the demo is available within the demo workplace.

When creating a layout you now can choose from a list of preconfigured templates:

Selecting a template will take over its layout definition (.xml), its code (.java) and additional resources (e.g. images) into your project. The layout that is created from the template will automatically work and is the starting base for your implementations.

The list of templates can be extended by own templates, so that typical layouts within your application environment can be quickly created.

The CaptainCasa tools now automatically detect the adequate level of re-loading runtime classes when applying changes during development. The very fast “Hot Deployment” is executed by default – a full re-load of the application is only done if really required.

For deploying your changes to the server-runtime there is only one central button left:

Dependent on the changes there are three different scenarios:

• The server-runtime does not require any re-loading at all (example: only resources were changed)
• The server-runtime is hot-deployed: only the UI classes are re-loaded – the “heavy” business logic is kept up and running. This is the typical case when developing UI classes.
• The server-runtime is re-loaded: the whole web application re-loaded. This is the typical case when changing the system as a whole (e.g. adding new libraries) or when e.g. updating database-related classes.

The automated detection is a significant simplification during development – before developers had to manually select the level of re-loading.

It is now possible to implement Page Bean Components in a simple way, that makes them directly use-able as “real” controls. Example: the following control…

…is internally implemented as Page Bean Component but is included into a layout by:

...
<demo:touchdate id="g_7" enabled="true" value="#{d.TestUI.dateValue}" />
...

Page Bean Component Controls are the next step to “componentizing” your project environment. They can be distributed in a simple way (by .jar file / Maven dependency) and they can be embedded in a simple way (as direct control).

Take a look into the technical documentation: HERE.

The CaptainCasa Toolset is available as SpringBoot application that can be loaded via Maven. As consequence you can automatically run exactly the version of the toolset that is required by the version of your project.

We now added corresponding documentation. Please directly read HERE or open the documentation page.

Changing the name of a page bean class, of a layout XML definition or of an SVG image means that you have to update direct and indirect references within you project – which is sometimes not totally trivial.

For this reason we added a refactoring tool in update 20220919.

When selecting a file of your project you will see all references to this file. Per reference you can decide if to include the file in the process of renaming.

Download the current update >HERE<.

Thanks to all of you who did send best wishes before and congratulations after last Sunday’s roadbike event – the “Ötztaler Radmarathon”. In short: it was a phantastic day – not only in the retrospective view but already during the event: perfect organization, perfect weather, great atmosphere, great landscapes – and last but not least: a super-stable roadbike without any technical problems. Some of you know that the bike’s base is a 30 year old steel frame, that was restaurated and equipped with modern parts in Bulgaria last year…

Who wants to join next year? – It is an extraordinary experience, I can guarantee!

Thanks again + Kind regards! Björn

Take a look into this article published in “Informatik Aktuell” (in German) :

(Click into image or >OPEN HERE<)

We moderately updated our default style following “material design”-principles.

Changes include:

• More space inside data grids
• Rounded popup borders
• Light background color behind input fields
• Buttons with border and mini-shadow
• Consistent usage of color schemes inside demos
• Gray colors a little lighter

Please take a look into our >online demo workplace< to view the full set of components. The updated style is applied as default to all new projects. Existing styles are kept, of course.