Download Progress Indicator

[skota]

Question1:
Is there anyway we can show the download indicator while loading the JS files?

One way we tried to solve this problem in Flash is download a very small file size which indicates download progress and then inernally it will download the bigger files and initialize it while progress bar is shown.

If you look at flickr interface they show a small animated gif while their engine is downloaded and initialised in the background. If we have to do some thing like that, it would be great if platform supports it automatically.

Question2:
W.r.t the activity indicator, when we make AJAX calls it would be best if the platform shows the server activity indicator, for example check out flickr interface when modify activity happens then they show a small indicator, do we have to explicitly write that indicator or platform supports it?

Question3:
When a transition from one Tab to another Tab happens in our case. It is taking a lot of time. (probably due to refresh problem that we posted in other thread) it would be good if such a transition happens then automatically system shows some kind of indicator poped up, so that the impatient user will be happy. Does the system doesn't support it by defuault using some API or we have to implement it?

Thanks,
-SK

[Isomorphic]

Hi skota,

Question 1: download indicator

If you use the FileLoader you can download SmartClient in the background while showing whatever type of loading indicator or start page you like.

We don't currently have a default loading indicator, but centering an animating .gif is very easy with basic HTML. You might also consider using the FileLoader to cache or load SmartClient during a login or registration process.

Question 2: communications activity indicator

Set RPCRequest.showPrompt to show a modal activity indicator. This happens by default for DataSource requests.

Question 3: manual activity indicator

You can do this manually via isc.showPrompt() and isc.clearPrompt(). However in this case it's almost certainly not going to be necessary, it appears to be a usage issue causing the slowdown - we'll respond in the existing thread for that issue.