🚀 go-pugleaf

wayne beech writes
> I have setting up an account which I would like to work as follows:
> 
> The person logs in and an application is autolaunched (easy enough).
> 
> The application then sets itself up so that no other application can be  
> accessed (done).
> 
> Finally (and the problem), once the user tells the application they are  
> done I would like for the application to log the account out.  I see no  
> way to do this with the WorkspaceRequest protocol....Is there a way to  
> accomplish this short of just killing the workspace or windowserver?
> 
> Any thoughts/comments/suggestions are appreciated.
> 
We saw no way to do this cleanly either.

The problem is that if you post a log-out event to the Workspace,
the workspace may wait for other applications to finish. 

The only option we found was to kill the Workspace itself.
*Not* a clean option.

Another option, if all you want to do is run your app,
is to use the loginhook option to loginwindow.
If you play with the default user of loginwindow, you can
set up a default account (like me) with no password, that
falls through and launches the loginhook.

(I believe if the loginhook returns an error value, this
will prevent the Workspace from launching, 
returning you to the loginwindow, but I can't remember.)

(I set the loginhook to be the myshell example, so I could
have a shell handly to see what was going on.)

Later,

John
-- 
John Robison - Oceania Health Care Systems 
john@oceania.com - NeXTMail Gladly Accepted

>wayne beech writes
>> I have setting up an account which I would like to work as follows:
>> 
>> The person logs in and an application is autolaunched (easy enough).
>> 
>> The application then sets itself up so that no other application can be  
>> accessed (done).
>> 
>> Finally (and the problem), once the user tells the application they are  
>> done I would like for the application to log the account out.  I see no  
>> way to do this with the WorkspaceRequest protocol....Is there a way to  
>> accomplish this short of just killing the workspace or windowserver?
>> 
>> Any thoughts/comments/suggestions are appreciated.

Since what you want sounds like you just want one app running that the
user logins to, messes with, then logs out, the easiest thing to do might
be to just make the workspace for that account the app.

dwrite loginwindow Workspace Appname

No dock, no ability to launch anything else, and when they quit the
app it logs out. Kinda cool to do Terminal as the login app, no dock! wierd.

la la la,
-- 
:: Christopher Lloyd :: a74k110@titan.ucc.umass.edu :: Yrrid, Inc. ::

In article <1992Aug7.220908.6594@nic.umass.edu> Chris Lloyd,
a74k110@titan.ucc.umass.edu writes:
>No dock, no ability to launch anything else, and when they quit the

Setting an application as a users default Workspace works fine as long as
the application doesn't do ANYTHING that relies on the Workspace (like
Services).

To be safe, its a good idea to use a nib editor like SegHoarker to
disable dangerous menu commands (like the Services menu).

Jeff Wishnie
jwishnie@csli.stanford.edu
Hey, don't get on my boss's case, I'm just speaking for myself.