With the Swallow client deployed, I figured it might be worth mentioning two things I learned about deploying a Widgetry based application. I've brought them up before, but it's worth mentioning again, in one place. So - say you've built your Widgetry based UI, and you are using Runtime Packager to package it. Step one:

The important point here is "Action on last window close" - you want to set that to "Continue processing". Why? Well, RTP is not (at present) aware of Widgetry, so when your first window opens at startup, the runtime manager notices that there are no UIs open - and promptly quits. So - implement a method in your UI that does this:

ObjectMemory quit

When you need to quit. Second, your application will likely use Widgetry dialogs, with class DialogUserInterface. Well, when you confirm/cancel a dialog, the Runtime system again notices that there are no Windows present (again, it's not aware of Widgetry) - so it quits. What you need to do there is create a noWindowBlock:

WindowManager noWindowBlock: [:mgr | true].

That just tells the runtime system to move along and ignore the "no window" state. Mind you, as Widgetry moves into deployment, these issues will get fixed by our engineers. If you are doing "bleeding edge" development though, it's useful testing information.

Technorati Tags: smalltalk