It looks as you add the content to it's body. An example is here:
http://www.resa-air.com/a5/be
Len
On Thu, 2006-12-07 at 20:09 +0530, Karthik N wrote:
> len,
>
> on your blog can you please post a screen shot of how the "Please wait"
> component display looks?
>
> Thanks
len,
on your blog can you please post a screen shot of how the "Please wait"
component display looks?
Thanks
if you can get the first bytes of the second (slow) page loaded you can
start that page with the html for a div to appear in the centre of the
screen in front of the "real" content.
The last thing on the page should be the html which moves this either away
to the left (negative coordinates) of t
Unfortunately, my problem is that I need it on plain links as well as
in forms. Nothing I can't fix by just assigning a new class to any
link that needs the handler and then adding the handler via a
javascript method which iterates over all elements with the
'pleaseWait' class.
--sam
Sounds
To avoid making multiple changes you could wrap your @Submit component
into a @CustomSubmit which passes all informal parameters and add's the
onClick and then overwritting the @Submit with @CustomSubmit in
the .application (worked in 3.* don't know about 4.*)
Len
www.len.ro
On Thu, 2006-12-07 at
On 12/7/06, Fred Janon <[EMAIL PROTECTED]> wrote:
>>It's probably more typing than my solution because of the number of
onClick handlers I'll have to add
Not sure if you can do it in your context, but instead of calling the JS
function in all buttons onClick, you could just call it in the FORM
o
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 n
It's probably more typing than my solution because of the number of
onClick handlers I'll have to add
Not sure if you can do it in your context, but instead of calling the JS
function in all buttons onClick, you could just call it in the FORM
onSubmit...
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
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
> ste
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 f
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 fi
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
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
If only it were easy to just turn to the PM and say "no, you're wrong.
We have a much bigger underlying issue that we'll be covering up with
this kind of fix. Instead of making users feel better as good
conservative use of wait/progress/etc indicators can do when not
abused - it will become a huge
Duly noted Sam, sorry for any assumptions I made.
If only it were easy to just turn to the PM and say "no, you're wrong.
We have a much bigger underlying issue that we'll be covering up with
this kind of fix. Instead of making users feel better as good
conservative use of wait/progress/etc indica
You are making some wild assumptions. My only performance problem is
waiting for some potentially latent web services to return some data
in real time and in performing some really huge db queries on an
already overworked database server. None of those slow loading pages
are spending any signifi
I hope you don't mind me saying so - and I know you will - but it
sounds to me like you have a lot more problems than what your current
web framework does/does not supposedly support.
I was afraid of as much while writing my last response on this thread
but held back to give you the benefit of a
On 12/6/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
It's hard to tell which problem you are trying to solve through your comments.
Well, I've got a lot of pages that just plain take a while (1-2 secs,
with a max at maybe 5 seconds for one particularly nasty page that
will eventually get some c
It's hard to tell which problem you are trying to solve through your comments.
The mention of a File upload area being a good place to have a wait
indicator would be a perfect scenario for the suggestion of throwing
up some sort of shared "wait" dialog via javascript. (as was outlined
in more det
I think that functions by loading the page entirely without data and
then firing off an ajax request to get the data. I'm seriously
considering reworkgin my pages in a manner that alows this. By
default, the page renders a page that does no work, including
populating models and such. The conten
Check the Panel component, from the YUI Library:
http://developer.yahoo.com/yui/examples/container/panelwait/2.html
Regards,
-Original Message-
From: Sam Gendler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 10:07 PM
To: Tapestry users
Subject: need "please wait" noti
The problem is that tapestry waits for the complete page to render
server-side before starting sending the response...
This is because it needs to gather all those js fragments that the
components
of a page might contribute.
The only way to disable this (that I know of) is to use neither @Shell
There are a lot of different ways to handle this.
A very quick and dirty way I've done it is by adding a dojo dialog
widget init block to my border and providing a global javascript
function call like "yourappname.showProgress()" that I can easily add
in to any potentially slow running form submi
24 matches
Mail list logo
