Path: utzoo!mnetor!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Suggestions
Message-ID: <1859@sugar.UUCP>
Date: 18 Apr 88 00:53:51 GMT
References: <8804170428.AA23977@jade.berkeley.edu>
Organization: Sugar Land UNIX - Houston, TX
Lines: 26

In article <8804170428.AA23977@jade.berkeley.edu>, SLMYQ@USU.BITNET writes:
> First, provide a public message port that receives WBStartup messages.  Its
> support code would just free the message, unload the SegList, etc. just like
> Workbench does.  That way programs which start their own Workbench processes
> could just point the ReplyPort to this and don't worry about when the program
> exits.

This doesn't need to wait for 1.x. I'm going to have a port like this in my
"Launch" utility... real soon now.

> It would have to be in Kickstart, not Workbench, because if Workbench
> isn't loaded and someone starts a Workbench-type process...

How about having it started in startup-sequence? If a program doesn't find
its port when it wants to start up a workbench process it can just do
an "Execute("l:launch-daemon", 0, 0);" first.

> Second, this one may be a not-so-easy one, but here it is.  Supply an extra
> window type, called SUPERTEXT...

A good idea. I was thinking of doing this for my console device replacement,
but I've gotten disillusioned about that.
-- 
-- Peter da Silva      `-_-'      ...!hoptoad!academ!uhnix1!sugar!peter
-- "Have you hugged your U wolf today?" ...!bellcore!tness1!sugar!peter
-- Disclaimer: These aren't mere opinions, these are *values*.