Yes, I've gotten familiar with this tool - very useful.
Except that MC loads, fileins, doits, etc.... all run in the UI
thread preventing access to the ProcessBrowser to see what is going on.
So when something runs amok - you're hosed.
On Jan 27, 2007, at 9:42 AM, David T. Lewis wrote:
Actually, Ned's ProcessBrowser does a good job of this right now.
Try playing around with it, you will be surprised at how easy
it is to pause and restart a background process, inspect it,
and interrupt it in a debugger.
Note also <http://bugs.impara.de/view.php?id=1578>, which makes
MVC and Morphic work the same way for background processes that
update the UI (it also has a small ProcessBrowser fix).
Dave
On Thu, Jan 25, 2007 at 12:54:14PM -0800, Todd Blanchard wrote:
I often wish Squeak worked that way by default.
Too many times I've kicked off a doit that ran for too long, then
began to wonder what it was doing, but the UI was frozen. This is
also true of fileins, etc. I would strongly support an effort to do
much less work in the UI thread and a clean feedback mechanism for
displaying progress and killing/suspending/debugging runaway items.
On Jan 24, 2007, at 7:39 PM, Ned Konz wrote:
So the approach that he took was to fork each script and arrange
for the UI to be updated from time to time as the individual
scripts are running.
_______________________________________________
Beginners mailing list
Beginners@xxxxxxxxxxxxxxxxxxxxxxxxxx
http://lists.squeakfoundation.org/mailman/listinfo/beginners
| 