Monthly Archives: June 2016

CaptainCasa is exhibitor at the JUGS conference in Stuttgart – a one day event that is organized by the Java User Group Stuttgart. Click on the image for more information:

There are couple of principles and components within CaptainCasa Enterprise Client RISC that are designed to support responsive/adaptive design.

First of all:

• All components in CaptainCasa can either be sized in a fix way (“100”)  or in a percentage way (“50%”). You can mix both ways without restrictions. This principle is consistent through all nesting levels of your component tree, and especially it is consistent both in horizontal and vertical direction.
• All adaptive/responsive components are not depending their internal sizing from the screen size or from the media type of the browser – but purely adapt their internal sizing according to the screen space they receive as component. This means: the adaptive concepts are not bound to a certain device type but they are available “everywhere”: if an adaptive component is started in a small popup-dialog then the component arranges its content in the same way as if it was started on a small device.
• You can scale the CaptainCasa dialog in any way by passing a “&ccscale=…” parameter to the URL that opens up the dialog.

Some of  the components that are explicilty designed to support repsonsive/adaptive scenarios are listed in the following gallery:

Talking about bugs is not a perfectly nice topic. But that’s what this text is about…

Some client side bugs are difficult to reproduce: they show up within your application but there might be problems to reproduce them within a simple context. Your application typically has quite some server dependencies, so it’s not really simple to transfer it to us…

We now provide a solution which already improved the level of service that we can five significantly within our Swing and FX client:

In your application you switch a certain record mode to “on” – and then you use the application just as normal. All http traffic (including image, JavaScript, …) is recorded into the file system. After having navigated and having experienced the (potencial) bug, you send the recorded files to us.

We are now able to run the client against a server, which takes all of its responses out of the previously recorded files. In other words: your server is simulated exactly in the same way it behaved when you recorded the information.

Please find detailed information here:

A new update was published.

• attribute STYLESEQ now consistently available for all CC-controls; using this attribute you can directly reference a CSS-style class
• you now can add own JavaScript programs properly using system.xml definition, please check the documentation “Developer’s Guide – RISC add-ons”
• component PDFRENDERRVIAURL is available
• component CLIENTHTTPSENDER is available – please also check the updated documentation…
• the value of attribute CLIENTNAME is now passed into the components DOM element’s name property
• …some bugs solved…

Please check the documentation area – there are two new documents available:

• “Developer’s Guide – RISC add-ons” provides information on selected RISC issues: adding own JavaScript files, adding/update style definitions
• “Subdevice Connectivity” provides information on how to couple the RISC Client with client side interfaces (e.g. Legic Card reader)