Comment 3 for bug 551630
Revision history for this message
| Borja López Soilán (NeoPolus) (borjals) wrote Re: Financial reports to review | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Just two notes:
- There is already a bug describing the General Ledger Performance problems (https:/
- The performance problem is not only about the time it takes to generate the reports (with 10000 account moves it takes >30 minutes to generate a general ledger report), but also about the fact that there is no feedback to the user and that the operation will eventually timeout (leaving the user no way to get his report). I really think we should have a real 'progress status' dialog for large computations that might timeout otherwise. It's not that hard to implement it server-side for wizards*, and with a bit of work on the client side we could make it work for reports.
------------
(*) We just need to start the calculations on a background thread, and return the client a "still working (XX% done)" like form. The client might then ask the wizard to refresh (currently this can be done manually using a "keep waiting" like wizard button, but we might implement an autorefresh on the clients).
When the job is complete (the wizard computation is done or the report file has been generated) the wizard instead of returning a "still working" form, would return a "done" form or the generated report file or whatever is the output.
Is not nice if the user has to press a 'refresh' button, but this actually works and prevents timeouts. We used a trick like this to display the progress on the "spanish fiscal year closing" wizard when it takes more than 20 seconds (see this image: http://