home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!comlab.ox.ac.uk!ph
- From: ph@physiol.ox.ac.uk (Patrick Haggard)
- Newsgroups: comp.soft-sys.khoros
- Subject: Re: That database issue
- Message-ID: <1992Dec22.102531.480@galen.physiol.ox.ac.uk>
- Date: 22 Dec 92 10:25:31 GMT
- References: <9212211332.PN24989@LL.MIT.EDU>
- Sender: ph@physiol.ox.ac.uk (Patrick Haggard)
- Distribution: comp
- Organization: University Laboratory of Physiology, Oxford University
- Lines: 20
- Originator: ph@galen.physiol
-
-
- In article <9212211332.PN24989@LL.MIT.EDU>, marshall@ll.mit.edu (Hunter Marshall) writes:
- etc.etc
- |> I'd like to throw out the idea of a utility to tap the comment fields
- |> of all the data files in a directory or registered with the browser.
- |> It could tap the full header. The information could displayed,
- |> held (a catalogue), or processed (ala awk/perl).
-
- I'ld like to support hunter's suggestion. The comment field would be a
- useful place to store things like image history, parameters of the image
- acquisition device etc. It would be useful to be able to read and write
- these fields from the program, either for a single file, or for all files
- as per animate's basename concept.
- The current comment field is only 1024 chars, which is actually pretty
- small. I can't remember the details for k2. Will the k2 header be
- extensible: if so, the comment area could be extremely useful for
- storing all kinds of things.
-
- Patrick
-