On Thu, 2006-12-07 at 03:45 -0800, Sam Gendler wrote: > I thought about doing that, but I wasn't convinced I could rely on all > browsers leaving the page visible until it received content for the > next page. Have you used this in IE 6 and 7, Firefox 1.5 and 2, and > Safari 2 by any chance? If not, I guess I'll check it out. It's > probably more typing than my solution because of the number of onClick > handlers I'll have to add, but it is a lot simpler and less likely to > have side effects. Thanks.
When I developed the site last year I tested it in Firefox 1.5, IE 6, and IE 5 (as the one installed at airline company at that moment). I think the only problem might arrise if the long waiting part is somewhere in a component. As far as I understand the process if the response takes some time to arrive then it's ok, if part of the page is rendered then a long wait occurs until the rest is fetched then it's not ok. I payed some attention to get into the first case. I did not got any complaints since then. Len www.len.ro > --sam > > > On 12/7/06, Marilen Corciovei <[EMAIL PROTECTED]> wrote: > > Here it is: > > http://www.len.ro/work/articles/please-wait-tapestry-component/view > > > > hope it helps, > > Len > > > > On Thu, 2006-12-07 at 01:53 -0800, Stefan Esterer wrote: > > > > > Hi! > > > > > > thx for your helpful description! > > > if you cound create a little simple example it would be great. > > > > > > thx for your effort > > > stefan > > > > > > > > > Marilen Corciovei wrote: > > > > > > > > The concept is simple. You have 2 pages. The one from which you go and > > > > the one which is supposed to follow which is rather slow. The first page > > > > contains a hidden div which gets visible when the user submits the form. > > > > This div is the one which you see with the animated gif. When the slow > > > > page has finished it's load it will replace the first page. This is > > > > based on the fact that the browser will keep the old page until the new > > > > one is loaded. > > > > > > > > <input jwcid="@Submit" > > > > listener="ognl:listeners.validateAction" > > > > value="message:validate" > > > > onClick="doWait(this, false);" > > > > /> > > > > > > > > The doWait just shows the hidden div/iframe. The only complicated part > > > > was to make the div/iframe about the combo boxes. If this is what you > > > > need I could create a working simple example. > > > > > > > > Len > > > > www.len.ro > > > > > > > > > > > > On Thu, 2006-12-07 at 01:24 -0800, Stefan Esterer wrote: > > > > > > > >> Hi.. > > > >> > > > >> and how did you get this working? > > > >> > > > >> thx > > > >> stefan > > > >> > > > >> > > > >> Marilen Corciovei wrote: > > > >> > > > > >> > I implemented something js based here: http://www.resa-air.com/a5/be > > > >> > while wanting for the flights results to come up. > > > >> > > > > >> > Len > > > >> > www.len.ro > > > >> > > > > >> > On Wed, 2006-12-06 at 13:07 -0800, Sam Gendler wrote: > > > >> > > > > >> >> Does anyone have a mechanism for displaying some kind of please wait > > > >> >> mechanism while waiting for a slow loading page to be rendered? I > > > >> >> can > > > >> >> think of a couple of potential solutions: > > > >> >> > > > >> >> 1. Submit form, have listener send to a please wait page which does > > > >> >> nothing but send another request which will actually load the page > > > >> >> in > > > >> >> question. The problems with this include pages that require lots of > > > >> >> data in the form submission. I'd have to stick it in the session or > > > >> >> throw it in a hidden form. If it is a lot of data, it could be > > > >> >> quite > > > >> >> slow. No control over when the browser stops displaying the > > > >> >> message - > > > >> >> usually first byte in. If there is network latency, that could > > > >> >> still > > > >> >> leave several seconds without the message in view. > > > >> >> > > > >> >> 2. If Tapestry supports it, I can render the header of the page, > > > >> >> including a div that says please wait, then flush to the browser > > > >> >> before initializing the model. At the end of the page, render some > > > >> >> js > > > >> >> that will hide the div. Only problem here is flushing before the > > > >> >> page > > > >> >> is completely rendered. Is this possible in Tapestry? > > > >> >> > > > >> >> Note: I cannot use an ajax update of the entire page and use the > > > >> >> effects available in an AjaxForm to render the message. At least, I > > > >> >> don't think I can. I haven't done an analysis of the pages in > > > >> >> question, but I'd really prefer top have my solution work on any > > > >> >> page, > > > >> >> rather than just on ajax-y ones. It would, however, be nice to > > > >> >> have a > > > >> >> solution which looks the same whether dong an ajax update (using > > > >> >> preEffect and effect) and when doing a full page reload after a > > > >> >> normal > > > >> >> POST. > > > >> >> > > > >> >> Thanks > > > >> >> > > > >> >> --sam > > > >> >> > > > >> >> --------------------------------------------------------------------- > > > >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> >> > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
