On 7/10/2010 19:32, kikiya wrote: > but of course threading is not a very elegant solution for this...
Why not? I have implemented this with success in different contexts. When I create a report that contains information about 10,000 customers, I show a progress bar that informs the end user that "6,000 out of 10,000 customers" were already processed. This works on a psychological level too. When you raise the time-out without giving any information about the progress, people wonder if something went wrong (for instance: did the server go down?), and they are tempted to hit "refresh" or "reload". If you inform them, time seems to go faster ;-) -- This answer is provided by 1T3XT BVBA http://www.1t3xt.com/ - http://www.1t3xt.info ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
