peter@sugar.UUCP (Peter da Silva) (06/18/88)
The referenced article described a system whereby you could have programs hiding in the backgroud with message ports connected to a menu manager that passed workbench menu events to them. It then went on to say that you could have a loader that hid there like that and loaded programs on menu selections. If you do it the other way: load and run programs directly in response to menu selections, you can do the same thing. Just divide your programs into an interface part and a work part. In fact there's a program out today that's laid out that way. FaccII. You load up FaccII and stick Facction in your browser menu. Voila. And it requires less code in memory, since you never have to leave a user interface loaded. I think more background programs should be built that way. What say? -- -- `-_-' Peter (have you hugged your wolf today?) da Silva. -- U Mail to ...!uunet!sugar!peter, flames to /dev/null. -- "A foolish consistancy is the hobgoblin of little minds".