This year’s Community Meeting will take place at Thursday, June 13. – The location of the meeting is Schwetzingen, close to Heidelberg.
We will provide detailed information about the agenda within the next weeks.
Please save the date!
This year’s Community Meeting will take place at Thursday, June 13. – The location of the meeting is Schwetzingen, close to Heidelberg.
We will provide detailed information about the agenda within the next weeks.
Please save the date!
We created a new “light style” that is provided as default style. Please take a look into our demo:
Click into image – or click HERE
From beginning on CaptainCasa provided a sophisticated hot deployment mechanism that is a significant accelerator during development: after changing your Java code you do not have to rebuild and restart your runtime (Tomcat, …) but classes are exchanged within the runtime “on the fly”. – CaptainCasa’s hot deployment itself is built on running the UI-related classes in some own class loader and restarting this class loader independent from the class loader of e.g. your Tomcat runtime.
Now there is interesting alternative which is especially interesting for projects which do not strictly separate the UI-related classes from the logic-related classes: the open source technology HotSwapAgent allows to exchange/update the classes that are loaded within your running Tomcat (or other runtime) dynamically. The installation and configuration is simple, we use the technology both internally and in customer projects in the meantime.
Please check the following documentation for details: Developing with HotSwapAgent
(This documentation is part of our official documentation site as well – section “Specific Documentation”.)
There is a new component that stores runtime configuration data. To be honest: this does not sound super-interesting… But: wait a second! Let’s explain the component using the default grid of CaptainCasa’s component library. The user can:
The new component plugs to the grid and stores all this configuration as a so called “usage variant”. The user can define several of these “usage variants” and can re-apply the corresponding configuration by simply double-clicking the variant.
One variant can be selected as default variant – and is invoked when accessing the grid.
The component that manages these usage variants is based on a super-simple Java-API.
public interface IExtractApply { public String extractData(); public void applyData(String variantData); }
So the component is not bound to managing the CaptainCasa’s grid configuration only! You can use the component for any aspect of your application where the user defines some runtime configuration that might be stored in order to simplify the usage of your application.
Drag & drop is not the number one area for finding great new features… – But: wouldn’t it be nice to immediately see where you can drop an item while dragging it? So that you do not have to guess for the locations that are potential drop targets?
Please take a view into the following video to see how the implementation of this feature adds significant usability to drag & drop operations.
The new component CAMERARECORDER is super-simple to use and manages the recording of videos by using the client’s camera and microphone. Videos are uploaded directly after recording to the server-side in order to be processed within your application.
The implementation consists out of: dropping the component into your page, defining its size – and deciding on Java-server-side how to process the video file. Of course, security is managed properly by the component – so that the user has to agree to the usage of both the client’s camera and the client’s microphone. The component automatically detects the available video and audio devices and lets the user select in case there is a choice.
What are the business scenarios for this component? Or is it just a “for fun”-component? – The concrete demand for the component is a quite nice one: in some scenarios the signing of a document must be recorded by a camera, so that it’s documented that the signature was done by the right person. – And of course there are lots of other scenarios: recording videos in the area of maintenance to better explain incidents. Recording questions of users during Q&A sessions. Documenting symptoms in the area of medical applications…
The component is available for desktop and mobile devices. The format of recording may depend on the client device.
Open our demo workplace, select the top item of the News section and take a look on your own!
The new NOTIFICATION component enables and simplifies the sending of notification messages to the browser client.
Notifications are shown as separate dialog which is managed by the operating system. Their appearance does not depend on the browser actually being visible – they also show up if the browser is minimized or if your current dialog is not the top-tab within your browser.
Please check the demo in the “News” section of our demo workplace.
Thanks to all of you having participated at yesterday’s community meeting in Schwetzingen!
Meeting you in person, receiving your feed back directly, discussing with you new features and feature requests – this is some strong motivation for us!
We are just about to collect all slides that were shown and will publish them inside the forum within the next days.
Thanks again + Kind regards! Björn
Please find details on this year’s Community Meeting HERE.
Everyone is invited to join who is interested in CaptainCasa Enterprise Client and/or is interested in Web-frontend technology in general. The meeting is a mixture out of overview information on the one hand and training on dedicated topics on the other hand.
We ask for registration by simple mail to info@CaptainCasa.com. Participation is free of charge.
Some content should show up for some while – and then disappear, or then shrink to some small size? That’s the purpose of the new component SIZEANMIATIONAREA.
Any content can be placed inside – and any content can be placed around. You define the from-width/height, the to-width/height and the duration after which the component should change its size. And after it is e.g. hidden you can trigger to re-show the component any time. Please take a look into the “News” section of the demo workplace.