Hi David,
the feature is just released, so now I'm collecting all comments for
next release's features. See my comments inline...
OK I'm actually trying it out now and it really is fantastic!
thanks a lot :)
Some feedback:
- make it automatically display the current job in the "Jobs" pane
(maybe a current project link that autorefreshes so you can always see
the detail for the current project)
If you're building with multiprocessing, than there can be more than 1
module in build. What should I pick as the best candidate?
- clicking Total Progress sometimes caused an error and wrote
javascript into the document (not serious as you can reload)
Unfortunately I cannot syncronize write (in perl) and reload (in
browser) operations - that's why sometimes there are errors.
What would be really nice as an enhancement is to be able to log all the
output of build to a file, and be able to click on the link for a
project / section but especially for an error, and see the actual output
for that section.
I'm thinking about it. Maybe, in next vesion there will be something
like that. So far I do not have a clear vision of how to handle these
logs. I mean where to write and when to remove.
I also thought in the past when doing my builds, it would be nice to
somehow record the average amount of time to do an initial build or a
rebuild for a given project, and use that information to work out the
overall progress (e.g. on Windows binfilter takes a long time to build
but some projects are very quick)
I think, this information is already there. You can see total build
time, CPU time (is different in multiprocessing mode) and times for each
directory (dmake times). Isn't it that what you mean?
Best regards,
Vladimir
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
