Author Archives: CaptainCasa

We scheduled this year’s community meeting for June 21st 2023 (Wednesday). The location is the same as in the previous years: Schwetzingen, close to Heidelberg. – Please save the date!

A new component in the area of “useful animations for business applications” was added. The FLYINCONTENTAREA component.

Changes to some content area are animated by “flying in” the changes from the point of the dialog, that initiated the changes. Using the new component is very simple – you do not have to deal with two content areas (the new one, the old one). All steps to leave the old content where it is  and to animate the new content on top of it are done automatically.

Please take a look onto the demo: HERE. – The demo is also part of our demo workplace. Click HERE to open the workplace.

The CaptainCasa runtime contains many functions ensuring the security of your web application. We now collected and condensed information about these functions into a technical document on its own – the CaptainCasa Security Guide. Read here what security aspects are covered and how to configure if required. Topics that are covered:

• restricting access to certain dialogs only
• preventing session hijacking
• Cross site scripting XSS
• Resource access, securing information that is kept inside your .jar libraries

The guide is a “must” for every developer and also responds to many questions that are typically asked for during security audits.

The documented was added to the documentation area as well.

“Hot Deployment” is the key to development efficiency for big projects! It reduces the duration between changing the code and testing it significantly. In the following “video from the labs”…

(click onto image or HERE to open)

…you receive on overview what it is and how to apply.

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.