Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!pro-abilink.UUCP!lexter
From: lexter@pro-abilink.UUCP (Sam Robertson)
Newsgroups: comp.sys.apple
Subject: (none)
Message-ID: <8905290916.AA04844@crash.cts.com>
Date: 28 May 89 11:29:16 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: pnet01!pro-sol!pro-carolina!pro-abilink!lexter@nosc.mil
Organization: The Internet
Lines: 25


Dave Lyons writes --

>Having resource forks doesn't let you do anything you couldn't have done
>with them.  On the other hand, they let you do things faster and typically
>with less code.  Sure, your programs *could* read everything you might ever
>want to custoze out of separate files--but they don't!

Yes, as a matter of fact if the resource files are to be implemented like the
Mac's then we will be able to have icons and various other information about
each file within the fork.  But, as of now (according to the last Tech Note I
read) they are not to be used nor to be tampered with in any software to be
released.  In other words? they are planning to standardize them for
something???

Sam
------------------------------------------------------------------------------
Applelink:  Lexter               || Sam Robertson   Pro-Abilink 300/1200/2400
GENIE:      SL.Robertson         || 1357 Santos           Sysop (Saw)
Proline:    Lexter@Pro-Abilink   || Abilene Texas 79605   (915)673-6856
INET: Lexter@Pro-Abilink.cts.com || UUCP: Crash!pnet01!pro-abilink!lexter
            ARPA:  Crash!pnet01!pro-abilink!lexter@nosc.mil
------------------------------------------------------------------------------
        " Tuesday Morning, please go away, I'm tired of you. 
           What have I got to lose. "      --   CSN&Y