OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

We are providing four one hour training sessions next weeek.

Mo/Tu/We/Th - each day at 16:00h, duration 1 hour.

Please contact us in case of interest - then you will receive the details and the Zoom login information.

Kind regards! Björn

We just are holding 4 one hour training sessions for learning the "CaptainCasa basics".

The sessions are recorded. Please follow the "News" section at the start of https://www.CaptainCasa.com - here you can find the recorded videos.

In the attachments of this post you can find the project to see the Java-source and the layouts that were developed during the session.

Thanks to all having come to Heidelberg/Schwetzingen for joining the XVIII. Community Meeting.

It was an inspiring and motivating event for us! ;-) And it was just nice to directly meet you!

Here you find the slides - even though most issues were demonstrated directly: https://captaincasa.com/pdf/20240613_CommunityMeetingXVIII.pdf

Kind regards! Björn

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

Hi,

you can place any additional JavaScript code, view first chatper of:

https://www.captaincasa.com/docu/eclnt_risc_developersguide_addon/

But to be honest: I do not believe that what is described in the article you mention is working for Single Page Application type of pages: as far as I see, the navigation is executed, but on the same page again: this means the current page should be reloaded... Anyway you may give a try: if you are successful, then we immediately copy from what you do! ;-)

KInd regards! Björn

PS: for interested readers: the common way to avoid unwanted back-navigation is to set CONFIRMEXIT to "true": then the default browser window shows up and the user has to confirm he/she wants to leave the application.

and PPS: another way it to start the dialog as progressive web application, then it runs in an own windows without the browser "surroundings"

...sorry, the previous message did not respond fully to your question. You are right (just check the code): the ccimagesize request is still fired. - If possible: use the naming convention then I guarantee for not firing any request...

Kind regards! Björn

...in the image the HEIGHT and the WIDTH are the space that is occupied by the image. How the image is rendered into this HEIGHT and WIDTH is defined by additional parameters:

KEEPRATIO=true now says, that the ratio of the image is kept during resizing
KEEPRATIOFITMODE=contain/cover defines how the image is "pressed" into the given HEIGHT/WIDTH, "contain" shows full image and shows remaining space as consequence, "cover" fills the region but cuts parts of the image.

Kind regards! Björn

Hi,

one way is to explicitly set IMAGEHEIGHT and IMAGEWIDTH in the IMAGE or ICON/BUTTON/...

Another one is to help the client with "proper" naming of images. If they end with "xxx_<width>x<height>.ext" e.g. "cancel_16x16.svg" then the client takes this as width/height and does not recalculate.

Kind regards! Björn

Hi,

should be a just normal value change. So if you want to get notified: set FLUSH to true and implement BaseActionEventFlush.

Kind regards! Björn

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

...sorry - this is an external framework which we embed. We cannot check for this kind of details ourselves! ;-) - Kind regards! Björn

Hi all,

when using the JSF reference implementation there is coming up a stack trace in the log when starting a dialog:

Code:

 java.lang.Error: javax.faces.FacesException: Expression Error: Named Object: org.eclnt.jsfserver.elements.impl.UNIFIEDPOLLINGComponent not found.
          |      at org.eclnt.jsfserver.elements.BaseComponentTag.createBaseComponent(BaseComponentTag.java:471) [eclntjsfserverRISC-20240514.jar:]
         |      at org.eclnt.jsfserver.elements.impl.ROWINCLUDEComponent$ParsedNode.render(ROWINCLUDEComponent.java:121) [eclntjsfserverRISC-20240514.jar:]
          |      at org.eclnt.jsfserver.elements.impl.ROWINCLUDEComponent$ParsedNode.render(ROWINCLUDEComponent.java:150) [eclntjsfserverRISC-20240514.jar:]

The application then continues with normal processing.
The error does no show up when using the "mini-JSF-implementation" of CaptainCasa.

We fixed this issue, fix is part of next week's update.

Kind regards! Björn

Hi Georgi,

yes, you are right - this is not perfect.
In short: we did an update here - for JEE it is available with interim update 20240516_INT2 (only on Maven, only JEE - complete installation is then coming next Monday).

Some more words: the column header is the one to receive the "click-events" on client side. Up to now only clicks were accepted when they werer originating from the header cell itself or from the label control inside. Now that you set the label size to 0, there was no event anymore.

Why did we exclude other controls (you know that in the browser click-events are bubbled up...)? If you place a FIELD into the header then you do not want to trigger a sorting because the user places the cursor into the field...

With our update we now also mark "stupid click events" (like clicking into a field) as events to not be processed for sorting. So we now can sort out the events in a clear way. Click on label is used, click on field is not used (if enabled...), click on button/... is not used.

Thanks for your message! Björn