Hi Marc,
You didn't quite understand how our uploader works. Try to think of uploader as a "text box", with a text box, you first "enter the text" and then submit. With an uploader you first "enter the files", then submit. There are two fundamental rules here:
1. The page has to be submitted in order to fire your server side code. This is an absolute rule. There is no escape for this one;
2. The file has to be transferred before the page is submitted. This is where our uploader is special. A regular HTML file upload element "upload" and "submit" at the same time. This way the whole file (all data posted by the client, including the file) first go into memory and then your code will have to save it onto the disk. Since it first load the whole request into memory, it's impossible for you to upload extra large file, also you can not get progress information. In order to stream the data into temp files on the server side and get progress data, files have to be transferred separately than the submit (which would also contains other form data). You can find an example at here demonstrating this concept:
http://www.essentialobjects.com/Demo/Default.aspx?path=AJAXUploader\_i1When you put the above together you would then see uploader does a two step process. However, if you set the uploader's AutoPostBack to true, it will automatically trigger the second step when the first step is done. In this case your user will only need one click.
"The should probably see the image right there" is a good idea, but I am not sure whether it should be part of our uploader. The uploader is generic file uploading tool and it is not just for images. Beside different people have different requirement, some want the image to be there, some don't. Some want it displays a small thumbnail, some want a big thumbnail and some may want a full image. Also different people have different layout design. Obviously these are just so much out of the scope of the uploader control.
Thanks