🚀 go-pugleaf

nathan@laplace.biology.yale.edu (Nathan F. Janette) writes:
> I'm going to catch hell for now knowing this, but...
> 
> How can a user "inform" the FileViewer that files with certain
> extensions should have a corresponding app selected as the default
> launch app?  It's easy enough to select an app already displayed in the
> Tools panel of the inspector, but how does one add a new choice?  Dragging
> an icon into that area doesn't seem to work (it should!)... 

Hmm, I'm not sure that it should.  Interesting idea, I guess.  I'm not sure  
that it shouldn't, either...   :-)

The application itself advertises what kinds of files it knows how to  
handle.  So the person writing the application has to put that part in.   
Then, the user has to put the application in one of the standard paths (ie,  
in /LocalApps, or ~/Apps, etc).  You could add more paths to the list of  
ones which are checked by changing the appropriate "defaults" value (which  
is "Workspace ApplicationPaths").

--
Garance Alistair Drosehn     =     gad@eclipse.its.rpi.edu
ITS Systems Programmer            (handles NeXT-type mail)
Rensselaer Polytechnic Institute;           Troy NY    USA

In article <1993Jan26.232845.12294@cs.yale.edu> nathan@laplace.biology.yale.edu writes:
> How can a user "inform" the FileViewer that files with certain
> extensions should have a corresponding app selected as the default
> launch app?  It's easy enough to select an app already displayed in the
> Tools panel of the inspector, but how does one add a new choice?  Dragging
> an icon into that area doesn't seem to work (it should!)... 

I havent tried this - but it may work.

You could edit the iconheader file of the relevant app, 
using otool or SegHoarker if necessary to extract/replace it.
(is that still necessary in 3.0?)
you could write one of those new fangled 3.0 filter services to
do any necessary conversion.

FileViewer seems to treat executable files differently - letting you use
Edit or Terminal as the default tool.  I'ld prefer Stuart, but since the choice
is not driven by the file extension - the above trick wont work.

This is where using file extensions as types starts to break down.
-- 
---------------------------------------------------
Alex Blakemore alex@cs.umd.edu   NeXT mail accepted

gad@eclipse.its.rpi.edu (Garance A. Drosehn) writes:

>Hmm, I'm not sure that it should.  Interesting idea, I guess.  I'm not sure  
>that it shouldn't, either...   :-)
I always have wished it did.

>The application itself advertises what kinds of files it knows how to  
>handle.  So the person writing the application has to put that part in.   
>Then, the user has to put the application in one of the standard paths (ie,  
>in /LocalApps, or ~/Apps, etc).  You could add more paths to the list of  
>ones which are checked by changing the appropriate "defaults" value (which  
>is "Workspace ApplicationPaths").

For me, I find that hitting Cmd-u and then waiting about 10-15
seconds (depending on network load and how big my ApplicationPaths
is) will do the trick.  It's not instantaneous, even when you put
the application in question on your dock.
-- 
David Lemson                                                (217) 244-1205
University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin
Internet : lemson@uiuc.edu                UUCP :...!uiucuxc!uiucux1!lemson 
NeXTMail & MIME accepted                           BITNET : LEMSON@UIUCVMD

In article <1993Jan26.232845.12294@cs.yale.edu> nathan@laplace.biology.yale.edu writes:
>I'm going to catch hell for now knowing this, but...
>
>How can a user "inform" the FileViewer that files with certain
>extensions should have a corresponding app selected as the default
>launch app?  It's easy enough to select an app already displayed in the
>Tools panel of the inspector, but how does one add a new choice?  Dragging
>an icon into that area doesn't seem to work (it should!)... 

You have to edit the __header portion of the __ICON segment of the
App.  The best way to do it is to pull it out of the App with
SegHoarker and change it with Edit.

The format goes a little something like this:


S	<extension>	<app name>	<icon name>


Those are tabs and not spaces...  So if you want to make Edit the
default app for tiff files for some reason, put this in the __header
portion of Edit:

S tiff Edit unknown


This will make Edit appear in the tools inspector.  Unknown just tells
the workspace to get the icon from somewhere else (in this case from
the OS, which already has a tiff icon).


andrew
-- 
andrew@cubetech.com      | "We cannot dwell in the time that is to come,
Andrew Loewenstern       |  lest we lose our now for a phantom of our
Cube Technologies, Inc.  |  own design." - Erendis      FYEO Public Key:
0000000701B61D1ADF0DFC9C16185CEA055200000007EB4A9FEB1922065D471A89E905B5