On Sun, Aug 26, 2007 at 10:44:50AM -0500, Bo Peng wrote: > > We can also use a simple Timer instead but the QSocketNotifier solution > > might be more elegant indeed. The simple dialog you are talking about > > could simply be a QTextEdit. > > Yes. The only difficulty is that QTextEdit is not allowed in src/support.
Emit a signal and catch it in the frontend? Or queue a user event? We'll need something similar mechanism for Alerts at some point of time anyway. GUI/core separation seems incomplete in this area (and that's not a Qt issue in this particular case, it our 'core steers gui' approach [which we all agree is wrong...]) > Our rule is that if something works, do not fix it. We will have to > show a clear advantage of switching to QProcess. Maybe that's a surprise to everyone, but I could think of a few: - less code to maintain on our side - simpler code (no #ifdef _FOO_PLATFORM_ anymore) - more people are likely to know the sematics of QProcess than of lyx::ForkedProcess - less comments of the '// Racy of course, but it will do.' kind. But that's just for the record. I do not really have strong feelings in this particular case. [(yet)]. Andre'
