Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!ncar!groucho!davis
From: davis@groucho.ucar.edu (Glenn P. Davis)
Newsgroups: comp.sys.next
Subject: Re: BAD NEWS FOR MAC -> NEXT PEOPLE
Message-ID: <9534@ncar.ucar.edu>
Date: 13 Dec 90 18:35:23 GMT
References: <1040@toaster.SFSU.EDU> <SCOTT.90Dec1000708@mcs-server.gac.edu> <	<36428@cup.portal.com>> <SCOTT.90Dec1135317@next-5.gac.edu> <351@heaven.woodside.ca.us>
Sender: news@ncar.ucar.edu
Organization: University Corporation for Atmospheric Research (UCAR)
Lines: 27

In <351@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes:

>In article <SCOTT.90Dec1135317@next-5.gac.edu> scott@next-5.gac.edu (Scott Hess) writes:
>>But, you might add, TIFF was specifically designed to be used as an
>>independant interchange format.  Tag Image File Format, and from the
>>specification memorandum:

>The real issue is a file format that allows graphics, text, images, and
>so forth to be stored without any significant limitations, yet still
>be editable (which means that any application should be able to open
>the file and read the data into its own data structures).  The closest
>thing I've seen so far to this is the Illustrator file format, which is
>supported by several applications on the Mac. There are, of course, other
>standards, like GKS and PHIGS and stuff like that, but these are not
>useful for Mac/NeXT portability, and besides, they have their limitations.

What about CGM? (Computer Graphics Metafile). It handles text, images,
polylines, polymarkers and polygons (filled or unfilled) with a
variety of attributes. It was designed and standardized to solve just
this problem. "Too limiting" or simply "Not invented here" ??

Glenn P. Davis
UCAR / Unidata
PO Box 3000                   3300 Mitchell Lane, Suite 170
Boulder, CO 80307-3000        Boulder, CO  80301

(303) 497 8643