<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 2, 2013 at 5:35 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think what I'm after is something like Pharo's headless UIManager,<br>
actually. The ReleaseSqueakTrunk build is hanging right now and<br>
there's no indication why. If I run the build script locally I can<br>
remove the -vm-display-null stuff and see the "Cleaning packages"<br>
progress bar, and so on. If I could hook into _that_, things would<br>
become a whole lot easier to debug. That, and having a script fail and<br>
log to stdout instead of bringing up a Debugger.<br>
<br>
I think I'll add that to the 4.5 wish list!<br></blockquote><div><br></div><div style>I've long wanted to push OmniBrowser's InteractionNotifications into the base. OB does all user interaction by raising a notification. The UI process catches the exception, does the interaction, and resumes with some kind of result. We do this in a few places, but it should be made comprehensive. </div>
<div style><br></div><div style>This scheme has two beneficial effects:</div><div style><br></div><div style>- it's possible to intercept interaction requests programmatically for scripts or headless situations</div><div style>
- it decouples low-level code from the UI, which should help with modularization and shrinking</div><div style><br></div><div style>Colin</div></div></div></div>