In building a Widgetry based runtime (the Twitter client that Michael and I have been working on), I've learned a couple of things that you'll run into. Mind you, these are transient issues that will go away as engineering deals with them (they'll be addressed as Widgetry moves into production) - but if you're out on the leading edge, here they are:

• When using the RTP to prepare your GUI app, for "Action on last window close", don't set "Shutdown image" - instead, set "Continue Processing". Then set up your own quit behavior
• Specify a custom NoWindowBlock - otherwise, when you open Widgetry based dialog boxes, you'll be in for a nasty surprise

The problem in both cases is that RTP currently makes assumptions about the kinds of Windows you have open, and doesn't "see" Widgetry based Windows. So in case (1) above, your image will quit as you start it. Very annoying :)

In case (2), dialogs prompt the NoWindowBlock as they close, which again, sees "no windows" and offers to open the launcher or quit - not what you want. I used this in my build script:

WindowManager noWindowBlock: [:mgr | true].

Not sophisticated, but it gets the job done for my little application.

Technorati Tags: smalltalk, widgetry, pollock