silverlight - HCI: make the user wait through everything up front, or amortize? -


I'm writing a Silverlight app that asks the web service to populate a tree control in each element There will be less than 2 level children, so something like this:

  a + -b + -cd + -g + -he + -i + -jf + -k + - L  

The Web service API is such that I can get only one hair node at a time, hence the first visit, I can get A, D, E, F. To get B, G, I, Kashmir, I have to make 4 trips. Similarly, I have to make 4 more trips to get C, H, J, L. (The service actually permits me to get all the nodes in a journey, but this does not give me parental relationships: - ()

My question is this: do I do this Should I get all the nodes for the tree view, or can I just get the top nodes, and get the other nodes on demand or in some background work? In addition, nodes are asynchronous I can change the form, so if I see all the nodes, then I'll need a "Refresh" button for the previewview, and if I'm on demand, then I will have a caching strategy.

Which is the best for a user?

A compromise where you face the first level And then load the rest if you load the nodes first (eg A, D, E, F, B, G, I, Kashmir You can redirect your shipments to focus on extended nodes recently (eg, A, D, E, FB, C) before the depth instead of R).

< / Html>

Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -