Author Archives: CaptainCasa

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:

A new demo “Stock Overview” is available within our online demo server. Click >HERE< for directly opening it .

When using the demo on a desktop device: resize the browser to see how layouts adapt to the available screen space.

Click >HERE< for viewing all our online demos.

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.