This is Default-application-to-launch-files-in in view mode; [Up]
Date: Sun 07-Nov-1991 23:41:07 From: zeke@znext (james dehnert) Subject: Default application to launch files in Heres the problem. When I use the Tools|Inspector|Tools in the workspace.app I dosen't give me the applications I really want a file to launch under. For example, If I inspect a file with the extention .diagram all I get is edit, which is not what I want. Question. How do I get another application in there? Thanks, Zeke
Date: Sun 08-Nov-1991 15:16:10 From: blakely@cpsc.ucalgary.ca (Michael Blakely) Subject: Re: Default application to launch files in In article <1991Nov7.234107.4950@znext> ash!znext!zeke(james dehnert) writes: > > When I use the Tools|Inspector|Tools in the workspace.app I dosen't give me >the applications I really want a file to launch under. For example, If I >inspect a file with the extention .diagram all I get is edit, which is not what I have a similar or the same problem. I have noticed that any files belonging to applications in the /LocalApps directory all default to edit files. Although if I put the application in ~/Apps the file types will then appear correctly. Then if I login as root the files belonging to applications in /LocalApps are ok. I have checked my path and /LocalApps is there. Any suggestions? Thanks in advance. Graham Lindgren
Date: Sun 08-Nov-1991 17:34:04 From: nathan@jacobi.biology.yale.edu (Nathan F. Janette) Subject: Re: Default application to launch files in In article <1991Nov8.151610.21820@cpsc.ucalgary.ca> blakely@cpsc.ucalgary.ca (Michael Blakely) writes: > I have a similar or the same problem. I have noticed that > any files belonging to applications in the /LocalApps > directory all default to edit files. Although if I put the > application in ~/Apps the file types will then appear > correctly. Then if I login as root the files belonging to > applications in /LocalApps are ok. I have checked my path > and /LocalApps is there. > > Any suggestions? Thanks in advance. O7. Applications installed in /LocalApps are not being found on my 2.0 system. Workspace has its own internal application path. In 2.0 /LocalApps was omitted. Improv needs to have /LocalApps in the Workspace path if you have Improve installed in /LocalApps. The work around in 2.0 only is: dwrite Workspace ApplicationPaths "~/Apps:/LocalApps:/NextApps:/NextDeveloper/Apps:/NextAdmin:/NextDeveloper/Demo s" (one continuous line! - pasc) This bug is corrected in 2.1, and hopefully all subsequent releases.
Date: Sun 08-Nov-1991 23:52:31 From: lee@pipe.cs.wisc.edu (Soo Lee) Subject: Re: Default application to launch files in In article <1991Nov8.151610.21820@cpsc.ucalgary.ca> blakely@cpsc.ucalgary.ca (Michael Blakely) writes: >In article <1991Nov7.234107.4950@znext> ash!znext!zeke(james dehnert) writes: >> >> When I use the Tools|Inspector|Tools in the workspace.app I dosen't give me >>the applications I really want a file to launch under. For example, If I >>inspect a file with the extention .diagram all I get is edit, which is not what >I have a similar or the same problem. I have noticed that any files belonging >to applications in the /LocalApps directory all default to edit files. Although >if I put the application in ~/Apps the file types will then appear correctly. >Then if I login as root the files belonging to applications in /LocalApps are >ok. I have checked my path and /LocalApps is there. > >Any suggestions? Thanks in advance. > >Graham Lindgren True. I had the same problem with my gif files. The symptom was that GIF files were recognized with ViewGif2 applications with icon of it ONLY WHEN I LOGGED IN AS ROOT. But, when I logged in my account rather than root, GIF files are shown with EDIT icons. As you noted you cannot drag the wanted applications into tool window associated with the target file. The quick fix was to save the target file under the application. Of course your application must be in the global "path" in .login file. As far as GIF I experienced is concerned, it works fine. For example, launch an application X, open the target file Y.t in which ".t" is tagged to be launched by application X so that all *.t files can be launched by X. Then save Y.t within the application X. AND at workspace, select Y.t and open tool for Y.t. Now you can see the application X on the window. Then choose application X within the window by click. Also click SAVE on tool window so that *.t files show icon of X and can be launched by X through double clicks. After update icons on workspace, you will see the file with icon of X and you can launch it without opening application X. Note that, if application does not have SAVE feature, you will not get the result as described above. I did not finish searching docs about this matter. But I strongly suspect that .NeXT/*[D,L] keeeps all correlations between applications and file extensions(MUST BE LESS THAN NO MORE 3 CHRs) for each user. NeXTime, Soo lee@cs.wisc.edu
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.