Enterprise Client Community

There are nicer ways, I believe:

Could you take a look at demo workplace: Components > Animation & Graphics & Sound > Image Capturer & Animator (1) - here select animation type "foglight" or "fogdark". The animations are super-easy to implement.

@cursor: the cursor is part of the style definition of each component. So... to consistently update the cursor we would have to update the style of each component. (How do we do it when communicating to the server: then a "glass pane component" is arranged in front of all other components, and this one glass pane component is driving the cursor styel...)

What do you think...?

Kind regards! Björn

(from mail - answered via forum)

Hi Björn,

Is there a way to somehow change the icon whenever there is a call to a bean to make some processing? Idea: We click on a checkbox then some filtering happens and the page is updated. If the process is to quick and the filter doesn't change the current UI, tthe user won't have a visual feedback unless we write something to the statusbar. He might get the impression that sthg "is broken". However if momentaneously the cursor icon of the mouse would quickly transit between the "default operation ongoing icon" (sand timer) and the default icon (pointer), he would know that there was sthg going on. What do you think?

Best Regards

Your way of accessing the top dispatcher is super-dependent on the way JSF stores its session data... Maybe you switched from a default implementation to our mini-implementation?

Nevertheless: if you cannot get the dispatcher by a concrete instance you can access by calling:

Code:

 IDispatcher top = DefaultDispatcher.getDialogSessionInstance();

Maybe you write a corresponding method in your dispatcher that returns back the proper class:

Code:

 public class Dispatcher
 {
     public static Dispatcher getDialogSessionInstance()
     {
         return (Dispatcher)DefaultDispatcher.getDialogSessionInstance();
     }

Kind regards! Björn

(question by mail - answered via forum)

I upgraded today from 20230731 to the 20240219 and found out that the method "HttpSessionAcccess.getCurrentHttpSession().getAttribute("d")" returns null when before we were getting a dispatcher. (See screenshot)

Can the top dispatcher still be accessed in this way but maybe another key?

Thank you

...is available in the download area.

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

IMPORTANT: please check change log - external client libraries were outsourced into own .jar libraries/artifacts with previous update 20240206

This is a bug in the toolset - thanks for telling us...

It happens when the project is configured to only hold resources in the webcontent (not in the source part). Please change your project configuration (.ccproject file in main directory of your project) to;

Code:

 <project ...
          resourcesinsource="true"
          resourcesinwebcontent="true"
          ...

Then you again see all tabs.
We will fix for next update.

Kind regards! Björn

(request by mail - answered through forum)

I updated CC to the latest version.
When I open the toolset I only see the "Web Content" tab - no "Source", no "Configuration" tab.

...is available in the download area.

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

IMPORTANT: please check change log - external client libraries were outsourced into own .jar libraries/artifacts with previous update 20240206

Hi Markus,

my ability to imagine things that happen on other screens than the one of myself is limited... ;-)

It would be great to add...

...screenshot of how it looks like
...XML layout how the image is embedded
...the image itself

If images are rendered very small (16x16) then it typically is an issue that the size of the image can not be properly calculated. But that's just a guess.

Hi Markus,

no asynch task because of this! ;-)

You have to logically chain the popups - the closing of the one popup will open up the next popup, until the user did all decisions.

There is an example in the demo workplace: General > Popup Dialogs > Chained Popups

Kind regards! Björn

Hi Roland,
thanks for sharing your experience!
Kind regards! Björn

Hi,

of course - two possibilities:

add style variant into your style:

Code:

 style.xml
 
     <tag name="t:link" variant="nobold" extendstag="t:link" extendsvariant="default">
         <set attribute="font" value="weight:normal"/>
     </tag>

or if going through CSS styling:

Code:

 style.xml
 
     <tag name="t:link" variant="nobold" extendstag="t:link" extendsvariant="default">
         <set attribute="styleseq" value="nobold_risclink"/>
     </tag>
 
 riscstyle_xxx.xml
 
 <stylesheet>
     <class n="nobold_risclink" extends="risclink">
         <var   n="@buttonFontWeight@" v="normal"/>
     </class>
 </stylesheet>

Kind regards! Björn

Dear community,

we plan to do this year's community meeting on Thursday, 13th of June.

Please check the date - we tried to check that it is not a pubic holiday in some part of Europe, that it is not in competition with the EM (starting the Friday after) and that there is no strike of any trade union.

Maybe we missed something? If so: tell us!

If not receiving negative feedback on this date from your side, we will then formally announce the meeting in 1 week.

Thanks + Regards! Björn

...is available in the download area.

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

IMPORTANT: please check change log - external client libraries were outsourced into own .jar libraries/artifacts!

Hi Joerg,

ROWINCLUDE is of course still supported, actually it is the internal base for the ROWPAGEBEANINCLUDE component.

So you still can use it.

The Page-Bean-inclusion-concepts are muchchchch simpler and nicer than the pure ROWINCLUDE... so for any continuation of development: use page beans. ;-) (You do not have tro convert everything: start at these places where you begin you development.)

Kind regards! Björn