ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I suspect it has something to do with the iframe inside the Div. Pretty sure browsers treat the iframe a little differently then the average block box.

The parent div by default should size to the fit the child contents. If the iframe content is static the I would suggest substituting it for a Facelet ui:include or a jsp jsp:directive.include. If you have to keep the iframe then add the width and hight attributes.

I'll try and make sure that someone takes a minute and updates the tutorials.

Make sure your are loading a ICEfaces style sheet first followed by your own to insure the cascade is correct.

Code:

 <link rel='stylesheet' type='text/css' href='./xmlhttp/css/xp/xp.css'/>
 <ice:outputStyle href="./css/yoursheet.css" />

There is a nice little plugin for Firefox called Firebug (http://www.getfirebug.com/) which can save a lot of time when trying to resolve CSS issues.

It is possible to page through a large data set of data without loading the whole data set into memory.

I'll try and get a more detailed explanation on our tutorial site when I get back from holidays but here is a run down on what can be done.

The DataModel class can be extended so that it reports back to the ice:dataTable the total number of records in the set but keeps its own internal list and offset of the records that make up a particular page of data.

A paginator listener can then be used to update the DataModel with only a subset of the total data on a change event. I have done this trick on several applications and the performance is quite good. I'll post a link to the tutorial when it is ready.

A simple style was applied to the component so that a user could see a few style options. Because panelBoard is a panel it is difficult to style it in a way that all users could use out of the box. In most cases this component needs to be tweaked to match the rest of the applications style.

The easies way to get rid of the style on the east panel is to override the following css class name in the XP theme.
Code:

 .icePageEast {
    background-color: transparent;   
 }

There currently is no way to general fully compliant html or xhtml. You can read more information about this issue at http://jira.icefaces.org/browse/ICE-1114

I suspect the background colour is coming from the border panel. If your using the ICEfaces 1.6 the style is coming from the css class name .pnlBrdrEast.

If you have any further problems please post the version of ICEfaces your using and if your using the xp or royale style sheets.

Could you post which version of ICEfaces you are running?

It is possible to show the loading message but you would have to use a new thread to do your searching. This would allows the initial requests initiated via the commandButton to return with an updated rendered attribute for the outputText. Once the new search thread finished the search you could update the bean states and inititiate a serverside render.

For a simple example of this see the progress bar demo in the component showcase.

In this example it is important that the renderBean is in Request scope to insure that concurrent DOM views work correct in this example.

The TransientRenderingExceptions are nothing to worry about as it is expected behavior. TransientRenderingException can occur do to network issues or in this case do to the fact that we keep creating the RenderBean In most application TransientRenderingException can be ignored but FatalRenderingException should remove them selves from the renderer.

Code:

if (log.isDebugEnabled() &&
         renderingException instanceof TransientRenderingException) {
     log.debug("Transient Rendering excpetion:", renderingException);
 } else if (renderingException instanceof FatalRenderingException) {
     if (log.isDebugEnabled()) {
         log.debug("Fatal rendering exception: ", renderingException);
     }
     intervalRenderer.remove(this);
 }

You can change the RenderBean scope from Request to Session to avoid the excessive TransientRenderingException but concurrent DOM views will not correctly work as a result.

Hello;

I tried to duplicate your problem in the component showcase but had no luck. Can you check that the method returning the images alt attribute is correctly setup.

alt="#{bundle.admin_management_access_rights_admin_help}"

If admin_management_access_rights_admin_help throws a null pointer the page may load once correctly but cease to function on any user interaction. Refreshing the page might show a stack trace in the browser and server logs.

Other than that everything appears to be in order.

When using ICEfaces you can using conditional statements via Facelets. Please see the getting started guide, chapter 4. The Timezone tutorial step 6 and 7 introduce how to use Facelets with ICEfaces. This will help you as well as show you some other powerful features in Facelets.

Attached is a content-type filter which insures that files loaded outside of the xmlhttp Servlet have the correct content types associated with them.

To try and simplify the configuration of filters I've setup my filter-mappings to point to all files loaded in images and css directories.

You'll need to make sure that you have image loading javascript to pre-load images. The filters insure that the header information is set correctly for the browser to interpret. Once configured, Tamper Data should show 200 status codes on the initial load and 304 when images are just loaded from the browser cache.

Hello Aamir;

Sorry for the delay on this reply. After a lot of testing and debuging it looks like there is a problem with filters if you are running ICEfaces 1.5.3 and Facelets.

I've been using a fire fox plugin called to Tamper to look at the HTTP header information being set for images and other content types.

The good news is that ICEfaces 1.6 dr3 will be out in a few days and addresses the issue with the previous release. I will attach another filter to make sure that content-type header information is set correctly for external resources, as it looks like Tomcat does not do this by default.

Patrick

Hello;

I took a quick look at your attached files and found a couple suspect lines in viewListingDetail.xhtml.

- First make sure you removed the embbeded ice:form. This will cause some headaches in the future as most browser and the ICEfaces bridge have a hard time with embedded forms.

- I suspect the IE issue is coming from the embedded tables that have width specified in percent. IE doesn't do a great job of figuring out what what parent block box width it will use to calculate the 100% of width. It often uses the body tag's width if a tag in the hierarchy is missing a width attribute.

- I would recommend adding borders to the div-table,table hierarchy so you can get an idea of what tag is causing the problem. Then remove the 100% width of the first embedded table to see if it causing the problem.

- Add a width="100%" to the main div. It has been my experience that this will often fix IE width issues, even know the default width should all ready be 100%.

- As a last resort you can added this table CSS attribute. It helps make IE behave a little more like FireFox. table-layout: fixed;

Hi Aamir;

I'll take a deeper look into this for you. What server are you running your application on?

Patrick