Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!swrinde!ucsd!sdcc6!beowulf!velasco
From: velasco@beowulf.ucsd.edu (Gabriel Velasco)
Newsgroups: comp.sys.next
Subject: Apps not iconizing properly.
Message-ID: <velasco.655498187@beowulf>
Date: 9 Oct 90 18:49:47 GMT
Sender: news@sdcc6.ucsd.edu
Lines: 27
Nntp-Posting-Host: beowulf.ucsd.edu

I have managed to successfully download binaries and sources from Purdue.  
I can uncompress them, untar them, compile them, and get them to run properly.
For some reason, I can't get the icons that come with some of the programs to
show up.  What am I doing wrong?

I used to put all of my NeXT binaries in ~/next-bin.  Now I have a ~/Apps
thinking that that might make a difference.  It doesn't seem to.  I have used
the 'install' and the 'mv' commands to put things in there.  That doesn't seem
to make a difference either.  Is there a difference between the two?  When I
select the programs on the browser, all I get is a generic application icon in
the window to the right side of the browser.  I never see the icons that came
with the application unless I examine them with the interface builder or the
tiff editor.  When I choose the make option in the interface builder, I don't
get a .debug file like the manual says I should.  Could this have something to
do with it?  How do I let the NeXT know which extensions are supposed to
automatically open an application?  For instance, how do I let NeXT know to
open ViewGif2.0 when I click on a .gif file?  I thought this was all taken care
of if you use the interface builder.  As I said, the applications work well.
There is just something screwed up in the highest level of the interface.

Thanks in advance.

-- 
                              ________________________________________________
 <>___,     /             /  | ... and he called out and said, "Gabriel, give |
 /___/ __  / _  __  ' _  /   | this man an understanding of the vision."      |
/\__/\(_/\/__)\/ (_/_(/_/|_  |_______________________________________Dan_8:16_|