John Pye wrote:
More coffee will only heighten my paranoia! Seriously, LyX is a GUI application but it makes no effort at being GUI-friendly during the document build process. It wouldn't be that hard to add a 'progress' dialog box for this stuff?
With current architecture yes, a bit hard. But I personally plan to add some more feedback (note that there is some feedback already in the status bar about LateX processing numbers).
Run a separate thread for the build tools and update the screen as they go?
A thread is an option. A "detached" process is cleaner though (IMO). Both options are very feasible and you are welcome to help us ;-) I personally plan to work on the second option and Peter K. has already worked on the first option IIRC.
Helps to know when images are too large or too detailed, or if something is hung, etc?
Everything's possible :-)
I think that this is a bug in LyX. LyX *must* be able to do this type of dependency tracking 100% correctly if it is going to attempt it at all. It is no good that it outputs the wrong document in this case.
Agreed.
I think that good architecture going forward might be for LyX to divest all of the build tracking stuff to an external program that specialises in dependency tracking, caching, and parallel building, and to try to re-use what others have already done in this area. Thoughts?
This makes sense IMO, but as usual nothing happens by magic. Abdel.
