🚀 go-pugleaf

In article <1992Oct25.001041.10847@u.washington.edu> wiml@milton.u.washington.edu (William Lewis) writes:
>In article <1992Oct15.125140.18223@pellns.alleg.edu> aherskow@alleg.edu writes:
>>Mostly the problem with any app is that you have to set Public Window Server 
>>on each machine you want it to run.  That makes things kind of "insecure" 
>>for the normal user (or Sys Adm.)  
>
>  This occurred to me as soon as someone mentioned a popup panel. However,
>it's possible (heh, heh) for root to extract the window server port from
>any running application. This can then be installed into a task that is not
>descended from the Workspace Manager, and in fact need not even have the
>same uid, or be running on the same machine. A "wall" daemon for the NeXT
>could check for a running copy of Workspace, extract all relevant ports,
>and create a subtask that can access the display &c. normally (as if it
>were descended from the WM). This subtask could then exec Zephyr.app or
>whatever.

Its easier than this. You don't need to ever be descended from Workspace
to talk to Workspace. Right now I have Terminal as my workspace program, and
one of the programs that I run at startup (from .login) is a script that
starts up Workspace.

From Workspace I run a little shell script (via LaunchPaths) that prints
out the $Workspace environment variable. I then set this variable in my
Terminal program, and presto! Instant communication with Workspace, from
an app that has never seen Workspace.

		Michael
Of course, this might just be dependent on the Window Server...

-- 
	Michael Gersten		michael@stb.info.com
NeXT Register Developer (NeRD) # 3860 -- Hire me! Quick!
Will program computers for food (and net connection, health benefits, cash,...)