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).
We started last year with a roadbike trip from Munich to Venice. This year we selected the Black Forest and the Vosges.
Day 1 was some constant up and down in the region south of Freiburg, passing Belchen, Feldberg and Schauinsland – climbing 2.600 meters of accumulated altitude… Day 2 was a bit more relaxing, riding up the Col de la Schlucht and taking the spectacular “Route des Crêtes” to the Grand Ballon.
And 2020? We try to form a small CaptainCasa team to register for >Oetztaler Radmarathon<. Users and partners of CaptainCasa are invited to take part! Please contact us via info@CaptainCasa.com.
A new component AREASELECTOR is available – with the main purpose of being able to crop images.
The component allows the user to select a certain area (e.g. on top of an image) and then passes the corresponding coordinates back to the application processing so that the image can be easily taken out of the original image using simple utility functions.
The component is not bound to image processing but can do any type of area selection on top of any components.
Some update in the area of focus management (“tab order”):
The tab order can now be explicitly defined using a new attribute FOCUSSEQUENCE.
The definition is done in some clever way and does not require to define tab number throughout all controls of the dialog – just the ones that behave different from the normal tab sequence need to be taken care off.
And: you now can define hot keys (keyboard shortcuts) behind components to directly move the focus into the component from where ever you currently are within a dialog. Use attribute REQUESTFOCUSHOTKEY accordingly.
Dear Community,
save the date: the XIV. CaptainCasa Community Meeting is scheduled for June 06th 2019 (Thursday). As usual the location is Schwetzingen, close to Heidelberg. Please find more details about the meeting >>HERE<<.
Participation is free, as usual. Please register by mail to >>info@CaptainCasa.com<<.
Regards, Björn
Please take a look into our new demo that shows a simple mobile application:
Please open from your mobile device >HERE<.
It uses components like:
The complete list of online demos is available >HERE<.
Take a look into the article that was published in the German “Informatik Aktuell” online magazine:
Click onto the image for reading the text or open the link >HERE<.
The component is part of our component portfolio for quite some time – but we see that it is rarely used… So we want to push the visibility a bit. Here is a short video “from the labs”:
CaptainCasa logs quite useful information – e.g. problems when accessing expressions, performance data about each single request processing – and of course details about errors.
By default the logging is done in the following directory:
<installationDir>/server/tomcat/work/Catalina/localhost/<webApp>/log_eclntjsfserver.txt.*
There maybe several log files (there are 5 rotating files into which the log is written), so sort the directory by date and pick the newest one.
The logging is configured in the file:
<project>/webcontent/eclntjsfserver/config/logging.xml
Please refer to the logging.xml_template file within the corresponding /webcontentcc-directory of your project.
During development it makes sense to use log level “INFO” and to directly output the log to the console, so that you can directly observe what happens. The log configuration to do so is:
<logging level="INFO" console="true"> </logging>
Using log level “INFO” means that each request is logged. In the log you see the processing in different phases. A really useful information is the list of the include-structure of the current dialog. Here you can find out, which layout definitions (.jsp definitions) are used, and how they are nested.
There are a plenty of other configuration parameters that can be used in the logging.xml configuration, each of them being described in the logging.xml_template file. Examples: