Enterprise Client Community

...thanks for the feedback. The patch will be included within the next official update (typically: "next Monday").

In case you/others require an offical update: please contact us!

Björn

Hi,

please find here some infos on updating an existing installation. These are especially usefult when not using the default installation (setup.exe ...) but working in an own Tomcat/... environment, e.g. based on Linux.

For updating you need to:

(1.) Download the version via DevZone. Either the setup.exe program ("all inlusive") or the .zip file. In both cases you will find a "resources" folder after installation/unzipping.

(2.) Now the first thing: update the CaptainCasa tools. This is the /webapplications/editor.war file. You need to bring this into the tomcat environment that you use. Pay attention: in the web application the project files are managed in /editor/config/projects. Although CaptainCasa will never overwrite this, it is useful to keep a safety copy - in order to avoid deletion because of other reasons (e.g. Tomcat removing a web application).
The most trustful way of bringing the editor.war into your tomcat:
a) stop tomcat
b) make sagety copy of /tomcat/webapps/editor/config/projects
c) remove tomcat/webapps/editor.war and tomcat/webapps/editor directory
d) start tomcat
e) throw the saved project files back in

(3.) Now you need to update your projects: each project contains CaptainCasa parts, so you need to update these parts. This is easy:
in the installation you find the directory /webappaddons. Copy the whole content of this directory into the /webcontent part you project.

(4.) Remember: next time you start the layout editor and looking into your project: by reloading the project files will be copied from the project's directory into the tomcat runtime - so you need to press reload one time to see the updated version.

(5.) OK, this is optional, but also to do: the installation contains the web application /webapplications/demos.war. Bring this into your tomcat environment as well. Best way: stop tomcat, remove webapps/demos.war and webapps/demos-directory, copy new demos.war and restart tomcat.

Of course: we recommend to define an ANT script or a shell script to execute all these steps at once.

Hope this helps!

Björn

...problem solved: the application was on old version. After copying webappaddons into the application project, "everything is fine".
Björn

...can reproduce. Only occurs (at least in my scenario) if page is explicitly reloaded. Explicitly reloading happens e.g. if changing the look and feel or the sizing factor. Will provide a solution short term...

Björn

Hi Agnes,

are these controls "just visible", i.e. not usable anymore, or are they still usable?

Björn

Hi,

well, what you do is exactly right. You need to decide what you want to do:

(1) Using the default popup, just reading the text from a different source than the file system => implement IOnlineHelpReader only - and pass back your file to be displayed.

(2) Doing whole online help management on your own => implement IOnlineHelpProcessor.

I double checked you example here. The interfaces are called correctly. - Is there a problem seeing the System-messages on your side?

Björn

...this should have to do with "your" style management: I believe any button has the minimum width of 100 pixels in your style...

Could you check?

Björn

Please find download + inforamtion inside the DevZone.

Björn

Hi,

up to now we said "no grid in grid", but at the end it was very simple to open up the grid management to recursively embed grids into grids...

Available with next update.

Björn

...your development speed is too fast. So, it's your fault.

Björn...

...forgot to mention: once having the dispatcher, you can ask this one (as you already mentioned) "getDispatchedBean()"...

Björn

Hi,

assuming that you use a sub-class of "DefaultDisptachter" (e.g. WorkpageDispatchter):

When extending your classes from "DefaultDispatchredBean" then the dispatcher is passed through the constructor and later on accessible via "getOwningDispatcher()".

This is the code of DefaultDispatchedBean, so you see: there is no magic behin. The Dispatcher - when creating a bean instance for a certain class - first checks if this class subclasses "DefaultDispatchedBean" (and then uses the specific constructor). Otherwise it uses the normal constructor without parameters.

Code:

 package org.eclnt.jsfserver.managedbean;
 
 /**
  * Default implementation of bean that is managed by a dispatcher. The bean
  * gets passed the dispatcher that is owning the bean via its constructor.
  */
 public class DefaultDispatchedBean
 {
     // ------------------------------------------------------------------------
     // inner classes
     // ------------------------------------------------------------------------
     
     // ------------------------------------------------------------------------
     // members
     // ------------------------------------------------------------------------
     
     private IDispatcher m_dispatcher;
     
     // ------------------------------------------------------------------------
     // constructors
     // ------------------------------------------------------------------------
     
     public DefaultDispatchedBean(IDispatcher dispatcher)
     {
         m_dispatcher = dispatcher;
     }
     
     // ------------------------------------------------------------------------
     // public usage
     // ------------------------------------------------------------------------
     
     public IDispatcher getOwningDispatcher()
     {
         return m_dispatcher;
     }
     
     // ------------------------------------------------------------------------
     // private usage
     // ------------------------------------------------------------------------
     
 }

Björn

Hi Frauke,

yes... (see Screenshot) - is part of next update.

Code:

         YESNOPopup ynp = YESNOPopup.createInstance
         (
             "Please read",
             "This is the content of the popup. Please either select YES or NO - or leave the popup by clicking the corner-close button.",
             new IYesNoListener() 
             {
                 public void reactOnNo()
                 {
                     Statusbar.outputMessage("No was pressed inside the popup.");
                 }
                 public void reactOnYes()
                 {
                     Statusbar.outputMessage("Yes was pressed inside the popup.");
                 }
             }
         );
         ynp.setShowCancel(true);

Björn

Hi,

we now changed the following way: coordinates are always relative to the "CaptainCasa Window". This makes things much easier and reflects the tpyical usage scenario much better.

Change is part of next update.

Björn

PS: in addition we updated as well, that left/top positions are scaled with the user's client settings

Hi,

(...please always post one item in one message... Thanks!)

with the first item (grid ... return ... tequila). If you get tequila: what's the error message on the server?

with the second: selecting a row does not mean that it receives the focus. For setting the focus you need to place the focus into an element witihn the row.

Focus not marked clearly: pls tell me which controls you mean: field, button, checkbox, radio button, icon, combo, etc. and many more clearly mark the focus - could you tell which control you mean? Thanks...!

Foldable pane: when the component is focussed (either field or icon) then pressing "space" opens/folds the component.

In a grid every control which is inside a grid is focusable - in order to allow the user left/right/top/down navigation on every cell.
If the grid only contains labels as cells then you are right: the focus is not visible (just the line that contains the focussed element is highlighed) - we will add the same "shading" as we added with combo and checkbox.

Björn