rich:calendar loading time

[shandor]

Hi
I have an app with multiple calendar objects on the same page ( 30 !!)
It takes the page a very long time to load and seems that it is due to browser side processing ( page is loaded via ajax ).

Is there any way to make things better, or to show to the user an ajax status icon a bit longer - until all components finish to load ? Seems that ajax status object is active only for the http traffic part but not for the actual browser side processing.

thanks
Adi

[nbelaevski]

Hello Adi,

Status should show activity for scripts processing also. What RF version do you use?

[ilya_shaikovsky]

Every calendar initializes its own objects on the page rendering. And time could differs in different browsers(IE6 results is worst than all)..

We already complete optimization task on this component. But we have to use separate objects for separate instances(because of some calendars features) so it results the performance in the cases like yours.

If you not satisfied with the initialization timing read
this article about possible workaround.
http://www.jroller.com/a4j/entry/richfaces_calendar_component_shared_calendar

[ilya_shaikovsky]

and b.t.w. do not miss Nick's questions about version. It's highly recommended to use latest one.

[shandor]

Thanks for your responses.

I am using 3.1.4 GA. It is a system deployed at a customer's site so I cant upgrade it right away ( btw, is this issue suppose to be better in later versions ?)

The customer actually have 80 (!) date boxes on one rich:panel component.
The panel is being loaded via ajax request. The browser is still crunching away long after the status icon is gone. In IE6, all the boxes appear immediately but the calendar buttons are coming up gradually, one after the other. The whole process takes around 40 seconds.

I will check the other solution Ilya suggested.

Adi

[ilya_shaikovsky]

https://jira.jboss.org/jira/browse/RF-1717

Calendar was improved as possible for this case. But anyway such case will not works fast especially in IE 6. The only solution at blog post I mentioned.

Probably we add some lazy pre-rendering additionally but it will be added not earlier that 3.3.2 and will not be backported to so old version.