Re: Apple2 archive at grind.isca.uiowa.edu

[andrep@balboa.eng.uci.edu (Andre Prellwitz)]

In article <284pjfINN9sg@srvr1.engin.umich.edu>,
Daniel Demaggio  <dmag@engin.umich.edu> wrote:

>Here at Umich, I have been putting a 4-line description at the
>beginning of the .BSQ files.  Someday RSN, I will write a program to
>extract these comments and make a neat-o-keen index file ala the
>umich mac archives.  I could even make mini indexes for each sub-dir.
>
>Since there are so many possibilites, let's get some feedback (for
>grind, and even existing FTP sites):
>
>Questions:
>1) Which do you want?
>   A) indexes for each subdirectory
>   B) indexes (i.e. foobar.txt) for each file
>   C) one global index

My vote is to have indices for each directory with 1-4 line comments on each
file, then one global index in the main directory with simple 30-40 character
description.  The global index should be a "quick map" to the actual file you
are looking for.  Its format could be as follows:

/apple2/system/cdevs/:
ZipGSCDev.SHK       13542  May 5'92  Controls the Zip GS from desktop
PhantasmDemo.SHK   245345  Apr 9'92  Screen blankers.  v3.1
   .
   .
   .
/apple2/system/fonts/:
BarCode12.SHK       23879  Jun23'93  A font for barcode scanners
   .
  etc.
The main index would only need size (in bytes) and date uploaded so all this
info could be read in one line.  Then, once you get this main index, you can
do a 'grep mainindex font' and all the fonts, fonteditors, etc., would be
displayed.  Saves time looking for a particular file.

>2) Do you want
>   A) BSQ files only
>   B) SHK files only
>   C) Both SHK & BSQ in same directory
>   D) Both SHK & BSQ in seperate trees

My vote is SHK files only.  Actually, it is no big deal if both reside in the
same directory, as long as they have an appropriate suffix.  But, .BSQ files
should be the ABSOLUTE FIRST files to go if disk space is at a premium.  They
take up more room, after all.

>3) Should the archive have:
>   A) 16 char filenames for all files
>   B) longer filenames (i.e. more descriptive)

Well, 16 characters for ALL files is a bit excessive, especially when a 10
character filename is enough :)  I think we can learn what NOT to do if we
look at some of the filenames on cco.caltech...  I wonder why some folders
are all caps, or why there are both NEW.FILES and HOT.FILES folders.  In the
Apple // world, new files _are_ hot files.  Also, 'hot' is subjective.  Then
there are filenames that are only 1-4 letters long.  I think acronyms are the
fad of the 80's; they suck, especially when there are no indices.  I think
people should be able to find the file they want without looking at the index.
The indices are there for convenience.

>E-mail responses or post discussion.. And happy hacking..
>-- 
>            -=- Dan DeMaggio -=- dmag@umich.edu -=-
>"That is really incredible. That is truly incredible.  That is so
>incredibly incredible that I think I'd like to steal it." -Zaphod


Finally, I think these conventions should be used for all Apple // archives.

email at: andrep@balboa.eng.uci.edu
---
The University of CA, Irvine, doesn't agree with me at all.