🚀 go-pugleaf

In article <1992Aug12.153419.4758@news.vanderbilt.edu>  
omar@talnext.cc.vanderbilt.edu (Omar Patino-Siliceo) writes:

>Hi NeXT-ers!

>This is probably a FAQ but I have to ask it anyway. Is it possible to add an  
>application to the "tool inspector" of a file (or set of files with the same  
>extension)? If so, how do you do it?

Each application keeps a list of what file extensions it can handle. It
is in the __header section of the __ICON segment. (you can manipulate
segments and stuff with SegHoarker, available from your favorite archive
site).

A typical application's iconheader looks like this: (also described
in NextDev bookshelf somewhere)
F <application name> <application name> app
and if it's a .app, we also have:
F <application name>.app <application name> pap
then come the list of file extentions:
S <extention> <application name> <long type>
i.e. the iconheader of WriteNow looks like:
F	WriteNow	WriteNow	app
F	WriteNow.app	WriteNow	app
S	wn	WriteNow	document
S	wndict	WriteNow	dictionary

So, it's straightforward to add a new extention to an application.

>Let's say that I would like to add Emacs so I could make Editor or Emacs the  
>default application for all documents with extension "letter". How do I go  
>about it? Thanks.

well, there's a default for this: Workspace DefaultOpenApp
For instance, when i tell EL2 (emacs listener. i think the
Emacs application now accepts file open messages now, but
i'm not sure at all.) to install itself,

mymachine% dread Workspace DefaultOpenApp
Workspace DefaultOpenApp EL2

So, you can just dwrite it to whatever application you want to use instead
of edit..

-nils

--
always have fun!\_________ I'm Nils McCarthy of the Center for Computation
it's me! nils@geom.umn.edu\___  and Visualization of Geometric Structures.
interface copyrights are evil!\______________________________________________
Hi! I'm a new generation of the .signature virus. Copy me to join in the fun!