Far too long page generation

[manu.blot@…]

Whenever a build fails and the user selects the build to observe the error, Bitten generates the log page for all the actions that have been successfully run. On large projects, there may be thousands of checked-out files prior to the compilation session.

It may takes dozens of seconds before the page is rendered (Trac 0.11b2), to discover that the path to a build tool is missing or some other trivial error, since Bitten is busy generating/decorating the very long list of checked-out files.

It would be very nice to have an AJAX-based log page, so that for example successful steps of a build are only shown upon explicit request. Only the failed step would be initially rendered, leaving short description for the remaining, successful steps. The user might be able to select a successful step so that the matching log is generated on-demand.

Flagging as "major" priority as on large projects, this makes Bitten really painful to use, but feel free to decrease the level if you don't think it's an issue.

[Emmanuel Blot <manu.blot@…>]

See also #284

[ebray]

I definitely like this idea, and may poke at it at some point if no one else does. How would you propose handling this situation without JavaScript though? I was thinking maybe show/hide filters for each build step. Just a submit button that can be clicked to turn each filter on and off. Without JS it would require a full page reload, but nothing to do about that.