@DATABASE VPI.guide @$VER: VPI_deutsch.guide 1.21 (30.04.97) by Thomas Igracki @AUTHOR Thomas Igracki @(c) by Thomas Igracki @WIDTH 78 @NODE Main "ViewProductInfo Anleitung" / @{b}V@{ub}iew@{b}P@{ub}roduct@{b}I@{ub}nfo / v1.21 von Thomas Igracki ___________________/ @{" C O P Y R I G H T " link Copyright} @{" Inhalt des Archivs " link Archiv } @{" Programmentwicklung " link History} @{" Was macht das Programm? " link WhatItIs } @{" Wie kann man mich erreichen? " link Me } @{" Aufruf des Programms " link HowToStart} @{" The Magic-User-Interface " link MUI } @{" Beschreibung der Menüs " link Menus } @{" Product-Info Fields " link PI } @ENDNODE @NODE Archiv "VPI/Inhalt des Archivs" Folgende Dateien sollten sich in diesem Archiv befinden: @{b}Product-Info@{ub} --> Product-Info Datei für VPI @{b}VPI.readme@{ub} --> kurze englische Doku @{b}VPI.liesmich@{ub} --> kurze deutsche Doku @{b}VPI.guide@{ub} --> Dokumentation im AmigaGuide Format @{b}VPI@{ub} --> das Hauptprogramm @{b}VPI.iff@{ub} --> IFF-Bild von VPI @ENDNODE @NODE WhatItIs "VPI/Was macht das Programm?" Mit diesem Programm können Sie sich sog. 'Product-Info' Dateien 'bequem', d.h. per Maus bedienbar (aber natürlich auch per Tastatur) ansehen. Es wird dazu das @{" MagicUserInterface " link MUI} von Stefan Stuntz verwendet. Klicken sie bitte @{" hier rauf " link "VPI.iff/main"} um zu sehen wie VPI aussieht. Oben links befindet ein Listview mit den in der Datei vorkommenden Feldern. Rechts daneben sind ein paar TextGadgets mit den wichtigsten Feldern, damit man sie auf einem Blick hat. Unten befindet sich schließlich das Listview, in dem der Inhalt des aktuellen Feldes angezeigt wird, er kann per Menü @{" Edit/Copy " link Menus 10} ins Clipboard kopiert werden. @ENDNODE @NODE HowToStart "VPI/Aufruf des Programms" @{b}Start von einer Shell:@{ub} [Run] @{b}VPI@{ub} @{" [] " link Args 1} @{" [SF=StartField] " link Args 5} @ENDNODE @NODE Args "VPI/Argumente des Programms" Der erste Parameter @{b}[]@{ub} ist optional (worauf schon die spitzen Klammern hinweisen!). Er gibt die Datei an, die geladen werden soll. Der zweite Parameter @{b}[SF=StartField]@{ub} ist optional (worauf die eckigen Klammenr hiweisen!) Er bezeichnet das Feld das nach dem Laden automatisch angesprungen und angezeigt werden soll. Falls keines angegeben wird, wird '.description' benutzt. @ENDNODE @NODE Menus "VPI/Beschreibung der Menüs" @{b}Project@{ub} @{b}Open...@{ub} - Öffnen einer 'Product-Info' Datei. Es erscheint ein FileRequester in dem man sich eine 'Product-info` Datei aussuchen kann. Sie muß foldendem AmigaDOS-Muster entsprechen: (.Product-Info|.Produkt-Info|Product-Info|Produkt-Info|#?.pi) @{b}About...@{ub} - Anzeigen von ProgrammName/-Version/-Release sowie ARexxPort. @{b}Quit@{ub} - Sofortiges beenden von VPI. @{b}Edit@{ub} @{b}Copy@{ub} - Kopieren des Inhalts des aktuellen Feldes bzw. des unteren Listviews. @ENDNODE @NODE History "VPI/Programmentwicklung" @{b}Release 1.21:@{ub} 37.11 (30.04.97): Fix: VPI sets now the background for the groups, listviews and textgadget to default so that you can change them via MUI-Prefs. @{b}Release 1.2:@{ub} 37.10 (02.10.96): New: VPI kann nun als DefaultTool benutzt werden! @{b}Release 1.1a:@{ub} 37.9 (23.11.95): Fix: Fix für MUI3, der Scrollbar fehlte bei dem Listview! @{b}Release 1.1:@{ub} 37.8 (28.08.95):·Bug: Das letzte Feld wurde nicht eingelesen. 37.7 (30.12.94):·Bug: Falls das StartFeld nicht gefunden wird, wird das 1. angezeigt! ·Neu: Falls die deutsche Sprache eingestellt ist, wird, falls kein Startfeld angegeben wird, erst nach '.beschreibung' gesucht. Wird es nicht gefunden, nach '.description'. ·Änd: Das Keyword 'SF=StartField' muß nicht mehr angegeben werden. 37.6 (24.12.94):·Neu: Lokalisiert 37.5 (22.12.94):·Neu: ctrl-c zum abbrechen, ctrl-f zum (de-)ikonifizieren. @{b}Release 1.0:@{ub} 37.4 (11.09.94):·Änd: Der 1. Parameter ist nicht mehr nötig, falls er weggelassen wird, kommt ein FileRequester. 37.3 (27.08.94):·Neu: Project/Hide zum verbergen des Programms ·Neu: ARexxPort-Name wird im About-Requester angezeigt 37.2 (23.08.94):·Bug: Falls die Datei ein Verzeichnis war oder nicht existierte. ·Neu: Menu "Edit/Copy" zum kopieren des Inhaltes des aktuellen Feldes ins Clipboard. ·Neu: Jetzt werden nur noch die Felder angezeigt, die vorhanden sind! 37.1 (13.08.94):·So, nun läufts erstmal! ·Shell-Support eingebaut 37.0 (12.08.94): Angefangen, da ich heute die FrozenFish CD bekam und ein Programm brauchte, womit ich mir die Product-Info Files komfortabel ansehen kann! Erstmal die Oberfläche programmiert. @ENDNODE @NODE Me "VPI/Wie kann man mich erreichen?" @{LINDENT 3} Falls ihr Verbesserungsvorschläge, irgendwelche Fragen, Bugreports usw. habt, dann könnt ihr mir schreiben, am besten per e-mail! Z-Netz: T.Igracki@Jana.berlinet.de UseNet: lokai@cs.tu-berlin.de -oder- T.Igracki@Jana.berlinet.de (bevorzugt!) URL : http://home.pages.de/~lokai/ Post : Thomas Igracki, Siegener Str. 34, Germany-13583 Berlin Viel Spaß mit dem Programm! @ENDNODE @NODE Copyright "VPI/Copyright" Copyright und andere rechtliche Dinge ************************************* Copyright (C) 1994 by Thomas Igracki Diese Dokumentation darf kopiert und weitergegeben werden solange die Copyright-Notiz und diese Erlaubnis unverändert auf allen Kopien enthalten ist. Es wird keine Garantie gegeben, daß die Programme, die in dieser Dokumentation beschrieben werden, 100%ig zuverlässig sind. Sie benutzen diese Programme auf eigene Gefahr. Der Autor kann auf *keinen* Fall für irgendwelche Schäden verantwortlich gemacht werden, die durch die Anwendung dieser Programme entstehen. Das Paket ist *freely distributable*, aber das Copyright liegt weiterhin bei Thomas Igracki. Dies bedeutet, daß es von jedem kopiert werden darf solange er nicht mehr als eine angemessene Kopiergebühr dafür verlangt. Diese Gebühr *darf nicht* höher sein als US $5 oder 5 DM. *Dieses Limit gilt auch für deutsche Public-Domain Händler!!* @{b}Außerdem wäre es nett, wenn man mir bei Gefallen des Programms eine kleine Gebühr bezahlen würde, so daß ich sehen kann, daß es sich lohnt an dem Pro- gramm weiterzuarbeiten!@{ub} Dieses Paket darf in Public-Domain Sammlungen aufgenommen werden (CD ROM Versionen dieser Sammlungen eingeschlossen). Die Distributionsdatei darf in Mailboxsystemen oder auf FTP Servern abgelegt werden. Wenn Sie dieses Paket weitergeben wollen, dann *müssen* Sie die originale Distributionsdatei benutzen. Die Programme und der Quelltext (oder Teile davon) dürfen *auf keinen Fall* auf irgendeiner Maschine benutzt werden, die für die Forschung, Entwicklung, Konstruktion, Tests oder Produktion von Waffen oder anderen militärischen Gütern benutzt wird. Dies gilt natürlich auch für alle Maschinen, die für das Training von Personen in *irgendeiner* der obengenannten Tätigkeiten benutzt werden. @ENDNODE @NODE MUI "The Magic-User-Interface" @{LINDENT 3} This application uses MUI - MagicUserInterface (c) Copyright 1993-96 by Stefan Stuntz MUI is a system to generate and maintain graphical user interfaces. With the aid of a preferences program, the user of an application has the ability to customize the outfit according to his personal taste. MUI is distributed as shareware. To obtain a complete package containing lots of examples and more information about registration please look for a file called "muiXXusr.lha" (XX means the latest version number) on your local bulletin boards or on public domain disks. If you want to register directly, feel free to send DM 30.- or US$ 20.- to Stefan Stuntz Eduard-Spranger-Straße 7 80935 München GERMANY Support and online registration is available at http://www.sasg.com/ @ENDNODE @NODE PI "Product-Info fields" @{LINDENT 3} The following are the fields defined by the Product-Info Specification v6 as designed by Fred Fish and Udo Schuermann (with some extra fields used by pitool!). @{" address " link .address } @{" aminet-dir " link .aminet-dir } @{" author " link .author } @{" construction " link .construction} @{" comment " link .comment } @{" contents " link .contents } @{" date " link .date } @{" described-by " link .described-by} @{" description " link .description } @{" distribution " link .distribution} @{" docs " link .docs } @{" email " link .email } @{" exectype " link .exectype } @{" fax " link .fax } @{" fullname " link .fullname } @{" installsize " link .installsize } @{" keywords " link .keywords } @{" locale " link .locale } @{" name " link .name } @{" phone " link .phone } @{" price " link .price } @{" reference " link .reference } @{" requirements " link .requirements} @{" restrictions " link .restrictions} @{" run " link .run } @{" short " link .short } @{" source " link .source } @{" stored-in " link .stored-in } @{" submittal " link .submittal } @{" tested " link .tested } @{" type " link .type } @{" version " link .version } @ENDNODE @NODE .address "Product-Info field: .address" @{LINDENT 3} @{fg shine}@{b}@{u}.address:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describe a full postal address of the author, to be used if it becomes necessary or desirable to contact the author. Do not specify the author's name, as this is already in the @{"author" link .author} field. @{b}FORMAT:@{ub} Multiple lines; formatting symbols n are not required, as physical line breaks are equivalent. @{b}NOTES:@{ub} SEE THE @{"author" link .author} FIELD FOR IMPORTANT INFORMATION @ENDNODE @NODE .aminet-dir "Product-Info field: .aminet-dir" @{LINDENT 3} @{fg shine}@{b}@{u}.aminet-dir:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Sets the directory where to put it on aminet. @{b}FORMAT:@{ub} 1 line, see below for a list of possible strings. @{b}NOTES:@{ub} @{b}All directories on Aminet@{ub} new Upload area priv Private uploads recent Files uploaded the last seven days biz Business software biz/dbase Data base software biz/dopus Directory Opus files biz/demo Demo versions of commercial software biz/misc Misc business type soft biz/patch Commercial software patches comm Communications comm/ambos AmBoS (BBS) related comm/amiex Ami-Express BBS related comm/bbs BBS programs comm/cnet CNET BBS related comm/dlg DLG BBS related comm/envoy Envoy network software comm/fido FIDO software comm/mail Mailing soft comm/maxs MaxsBBS related comm/mebbs MEBBSNet BBS related comm/misc Misc communications comm/net Networking comm/news Newsreaders comm/tcp AmiTCP networking comm/term Terminal programs comm/ums Universal Message System comm/uucp UUCP software comm/xeno Xenolink BBS related demo Gfx and sound demos demo/40k 40K intros demo/aga Demos requiring AGA chipset demo/disk Demos on diskettes demo/ecs Demos for the ECS chip set demo/euro Euro demos in file form demo/file Single file demos demo/funet From the Funet collection demo/intro Intros demo/mag Demo coder magazines demo/mega Euro demos requiring floppies demo/slide Image oriented demos demo/sound Sound oriented demos demo/ta95 The Assembly 1995 demos demo/tg93 The Gathering 1993 demos demo/tg95 The Gathering 1995 demos demo/tp92 Demos from The Party 92 demo/tp94 Demos from The Party 94 demo/track Trackmos dev Development software dev/amos AMOS BASIC compiler dev/asm Assembly language related dev/basic BASIC language related dev/c C language related dev/cross Cross development dev/debug Debugging software dev/e E language related dev/gcc GNU C compiler dev/gui GUI builders dev/lang Various languages dev/m2 Modula-2 related dev/misc Misc development software dev/moni Monitors/disassemblers dev/obero Oberon related software dev/src Tutorial sources disk Disk/Harddisk tools disk/bakup Backup software disk/cache Disk caching disk/cdrom CD-ROM related software disk/misc Various disk related tools disk/moni Disk monitors disk/optim Disk optimizers disk/salv Disk recovery software docs Text documents docs/anno Announcement documents docs/etext Project Gutenberg books docs/help Help on various issues docs/hyper Hypertext documents docs/lists Lists and tables docs/mags Magazines docs/misc Various documents docs/rview Amiga product reviews game Games game/2play 2 and more player games game/actio Action games game/board Board games game/demo Demos of commercial games game/gag Gag programs game/hint Game hint documents game/jump Jump-n-run games game/misc Miscellaneous games game/patch Patches for games game/role Role, adventure games game/shoot Shoot-em-up games game/think Mind games game/wb Workbench games gfx Graphics gfx/3d 3D graphics software gfx/3dobj 3D objects gfx/aga AGA chip set softwaare gfx/board Custom gfx board software gfx/conv Gfx conversion tools gfx/edit Paint programs gfx/fract Fractals and Mandelbrots gfx/misc Misc graphics software gfx/pbm Pbm+ gfx conversion gfx/show Image/anim displayers gfx/x11 Amiga X-Windows hard Hardware hard/drivr Drivers for hardware hard/hack Selfmade hardware hard/misc Misc hardware related files info General FTP information info/adt Machine readable filelists info/index Various Aminet index files info/sites Info on other FTP sites info/start Beginner information info/stats Statistics about this site misc Miscellaneous misc/amag German Amiga Mag PD misc/antiq Nostalgic stuff misc/edu Educational software misc/emu Emulations misc/math Mathematics misc/misc Uncategorizable misc/sci Scientific software misc/unix Amiga related UNIX software mods Music modules mods/8voic 8-voiced songs mods/airon Mods by Airon mods/boing Boing collection mods/chart Module hits mods/chip Mods without samples mods/ctp MODs by Counterpoint mods/demo Demo style music mods/ephnx Modules from Euphonix mods/fby Mods by Fabio Barzagli mods/funet Funet collection mods/funk Funky/jazzy mods mods/hardc Hardcore techno mods mods/hje Mods by H.J.Ehrentraud mods/hw Mods by Hillware mods/instr Instrumental mods mods/jogei Mods by Jogeir Liljedahl mods/jungl Jungle/Breakbeat mods mods/maxym Mods by Maxym mods/med MED modules mods/misc Miscellaneous songs mods/mpeg Samples in MPEG format mods/otis Modules by Otis mods/piano Piano mods mods/pop Pop music mods/pro Protracker songs mods/przk Modules by Parzek mods/rated Misc rated modules mods/s3m Multichannel S3M mods mods/smpl Sound samples mods/sets Module collections mods/spark Modules by P.D. Spark mods/sidew Modules by Sidewinder mods/slc Modules by Slice mods/slow Slow/melodic mods mods/synth Synthesizer modules mods/rock Rock'n'Roll mods/techn Techno music mods/tranc Trance techno mods mods/voice Music with voices mods/xm Multichannel XM mods mus Musical software mus/edit Composing software mus/midi MIDI software mus/misc Miscellaneous mus/play Sound players mus/smpl Sound samples pix Pictures pix/anim Animations pix/astro Astronomy pictures pix/art Hand drawn imagery pix/bill Bill Graham traces pix/clip Clip art pix/eric Eric Schwartz anims pix/fauna Animals pix/fract Fractals pix/guard Guardians traces pix/icon Icons and backdrops pix/illu Illustrations pix/imagi Imagine traces pix/irc The people on IRC pix/misc Miscellaneous images pix/mwb MagicWB icons pix/real3 Real3D traces pix/sport Sports pictures pix/trace Raytraced pictures pix/vehic Vehicle images pix/views Scenery, countries pix/wb Example WB screens text Text related text/bfont Bitmap fonts text/dtp Desk top publishing text/edit Editors text/font Fonts of all formats text/hyper Hypertext tools text/ifont Compugraphic IntelliFonts text/misc Misc text software text/pfont Adobe Postscribt fonts text/print Printing tools text/show Text displayers text/tex TeX formatting package util Utilities util/app Appicons, appwindows util/arc Archivers util/batch Script software util/boot Startup sequence software util/blank Screen blankers util/cdity Commodity type software util/cli Command line interface util/conv File conversion util/crypt Encryption tools util/dtype Datatypes for OS 3.x util/dir Directory utilities util/gnu GNU utilities util/libs Libraries util/misc Miscellaneous util/moni System monitors util/mouse Mouse accelerators util/pack Packers util/rexx AREXX tools util/shell Shells util/sys Commo file replacements util/time Clocks and timing util/virus Virus checkers util/wb Workbench utilities @ENDNODE @NODE .author "Product-Info field: .author" @{LINDENT 3} @{fg shine}@{b}@{u}.author:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} Any and all authors who have a part in the program @{b}FORMAT:@{ub} Any number of lines, treated as one line (n in the text will "break up" the line into multiple visual lines.) @{b}EXAMPLE:@{ub} Joe R. User, Tea Rexx. @{b}EXAMPLE:@{ub} J. Jonesn Random Hackern B. Clinton @{b}NOTES:@{ub} Addresses should be placed in the @{"address" link .address} field. There should be only one @{"address" link .address} field for each @{"author" link .author} field. If more than 1 @{"author" link .author} field is specified, then the same number of @{"address" link .address} and @{"email" link .email} fields must also be given in a 1-to-1 relationship (i.e. the 3rd @{"author" link .author} field must be associated with the 3rd @{"address," link .address,} and the 3rd @{"email" link .email} field.) EX: see the example "Joe R. User, Tea Rexx" above; Assume that Joe R. User has long vanished and no known address, but that Tea Rexx has supported the program for a while. If an @{"address" link .address} and/or @{"email" link .email} field is available for Tea Rexx, then you must specify EMPTY @{"address" link .address} and/or @{"email" link .email} fields for the author listed BEFORE the ones for Tea Rexx. Likewise, if the two authors names were reversed, you would NOT have to specify blank @{"address" link .address} and/or @{"email" link .email} fields for the second author. I hope that makes sense. @ENDNODE @NODE .construction "Product-Info field: .construction" @{LINDENT 3} @{fg shine}@{b}@{u}.construction:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describe the type of language(s) used to create this program and the methods used to build the final executable. If possible, include the compiler version(s) and possibly important options, such as optimization. @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more information. @{b}EXAMPLE:@{ub} SAS/C++ 6.5 with full optimization. @{b}EXAMPLE:@{ub} AdaEd. @{b}EXAMPLE:@{ub} Fortran with self-made compiler. @{b}EXAMPLE:@{ub} AMOS @{b}NOTES:@{ub} This is usually closely related to the @{"exectype" link .exectype} field but differs from it in that the @{"exectype" link .exectype} might be "Compiled C" but the compiler used was "RottenC 0.97" @ENDNODE @NODE .comment "Product-Info field: .comment" @{LINDENT 3} @{fg shine}@{b}@{u}.comment:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .contents "Product-Info field: .contents" @{LINDENT 3} @{fg shine}@{b}@{u}.contents:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .date "Product-Info field: .date" @{LINDENT 3} @{fg shine}@{b}@{u}.date:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} The program's official release date; not the date it made it into the database. @{b}FORMAT:@{ub} year.month.day 1 line only @{b}EXAMPLE:@{ub} 1993.09.27 @{b}NOTES:@{ub} The date format is chosen to be easily sortable. Note the use of leading zeros in month and day. The full year is to be given in anticipation of the coming change to a new millenium. @ENDNODE @NODE .described-by "Product-Info field: .described-by" @{LINDENT 3} @{fg shine}@{b}@{u}.described-by:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Specifies who created the description (Product-Info file) for the program. @{b}FORMAT:@{ub} Free form; should include an electronic mail address, too, if available. @{b}EXAMPLE:@{ub} Fred Fish (fnf@fishpond.cygnus.com) @{b}EXAMPLE:@{ub} Udo Schuermann @ENDNODE @NODE .description "Product-Info field: .description" @{LINDENT 3} @{fg shine}@{b}@{u}.description:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} A full-text description of your program, containing anything that is NOT ALREADY available through the other fields (see above and below.) The reader should gain a good understanding what your program can and cannot do. If you mention other programs please do not forget to provide a @{"reference" link .reference} field for each such mention. @{b}FORMAT:@{ub} Any number of lines, treated as one line. Formatting is permitted, but generally discouraged. @{b}NOTES:@{ub} Do not indent your text if you choose to format your text into multiple paragraphs. Do not use t as a tab. Leave paragraph formatting to KingFisher. @ENDNODE @NODE .distribution "Product-Info field: .distribution" @{LINDENT 3} @{fg shine}@{b}@{u}.distribution:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describes the distribution and ownership status of this software. Please see below for a list of common (and recommended!) terms to use. @{b}FORMAT:@{ub} 1 line @{b}EXAMPLE:@{ub} Shareware @{b}NOTES:@{ub} Please see the table below for descriptions of the recommended terms. LIST OF SOFTWARE STATUS KEYWORDS Commercial Commercial software is owned and distributed through licenses. It costs money to individual end-users and is not freely distributable. SUCH PIECES SHOULD NOT APPEAR ON DISKS THAT ARE MEANT FOR FREELY DISTRIBUTABLE SOFTWARE! Commercial Demo Represents a demonstration of a commercial package. As such, commercial demos are freely distributable and may have limitations as described in the .limitations field. Giftware Like shareware, usually. Shareware Such software is owned and copyrights are held by the author(s). The software may be distributed freely, but not sold for profit, of course. Shareware often specifies a limit of some time after which you are requested or required to register the software (i.e. pay for it.) This provides you with the means to evaluate the software thoroughly before paying for it. Freeware Such software is owned and copyrights are held by the author(s). The software may be distributed freely, but not sold for profit, which would mean the software is no longer FREEware. No payments are required for such software. Public Domain Software labeled PD (Public Domain) belongs to the public, i.e. ANYONE. Some people release their software into the public domain with the mistaken idea that they can continue to own and control the program. Not so. Software that is labeled Public Domain (or said by the author to be released into the public domain) truly belongs to anyone and everyone. It is quite legal for someone to take such a program and sell it for profit as is. Likewise, it it perfectly acceptable to modify public domain software to build a better product (or whatever) out of it and then sell it for profit. GNU Public License The terms and conditions of this license are long and not easily reproduced here. Suffice to say that software released under the GNU Public License must be distributed with source code. They are not public domain, however. GNU Library Public License The terms and conditions of this license are long and not easily reproduced here. Suffice to say that software released under the GNU Library Public License must be distributed with source code. They are not public domain, however. Copyright but Freely Redistributable The author holds all copyrights but allows the material to be freely distributed under specified conditions. @ENDNODE @NODE .docs "Product-Info field: .docs" @{LINDENT 3} @{fg shine}@{b}@{u}.docs:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} List all documentation files, possibly for viewing from within KingFisher for more detailed info. @{b}FORMAT:@{ub} 1 line per file @{b}EXAMPLE:@{ub} HomeBase.guide HomeBase.dvi HomeBase.doc @{b}NOTES:@{ub} KingFisher examines the EXTENSION and invokes the appropriate viewing tool: MultiView/AmigaGuide for .guide files, ShowDVI for .dvi files, more for anything else. These files can also be sent to the printer via KingFisher (i.e. print .ps or .doc files.) KingFisher will honor the PAGER environment variable (defaults to 'more') to display standard text. @{b}NOTES:@{ub} Omit any path to these files, unless it is a relative path from within the program's CD-ROM or disk directory. Do not specify these files if they are located within archive files; remember: the files must exist as they are given here! @ENDNODE @NODE .email "Product-Info field: .email" @{LINDENT 3} @{fg shine}@{b}@{u}.email:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describe a full electronic mail address. Make sure that this address is complete and reachable even from less well-connected sites. The author of KingFisher, for example, can be reached as walrus@wam.umd.edu It would be an error to specify only "walrus" or "walrus@wam" even though these will work within the particular organization where this address is valid. @{b}FORMAT:@{ub} Multiple lines; formatting symbols n are not required, as physical line breaks are equivalent. Do not specify more than one email address per line. The more you abide by RFC-822 specifications the better. @{b}EXAMPLES:@{ub} walrus@wam.umd.edu (Udo Schuermann) Udo Schuermann "Udo Schuermann" Udo Schuermann @{b}NOTES:@{ub} You may specify multiple electronic mail addresses in order of decreasing reliability and permanence, each on its own line. SEE THE @{"author" link .author} FIELD FOR IMPORTANT INFORMATION @ENDNODE @NODE .exectype "Product-Info field: .exectype" @{LINDENT 3} @{fg shine}@{b}@{u}.exectype:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describe the type of executable(s) that make up your program. Examples: 68xxx, AMOS, Script, ARexx, Compiled basic, Amigabasic, etc. @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more information. @{b}EXAMPLE:@{ub} AMOS @{b}EXAMPLE:@{ub} 68000, 68020, and 68040. @{b}EXAMPLE:@{ub} Compiled BASIC @{b}EXAMPLE:@{ub} Compiled ARexx @{b}NOTES:@{ub} AMOS-based software has been said to not work on some systems at all; this entry allows a user to determine if the software is worth obtaining in the first place. @ENDNODE @NODE .fax "Product-Info field: .fax" @{LINDENT 3} @{fg shine}@{b}@{u}.fax:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .fullname "Product-Info field: .fullname" @{LINDENT 3} @{fg shine}@{b}@{u}.fullname:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} The program's full (or complete) name @{b}FORMAT:@{ub} 1 line only @{b}EXAMPLE:@{ub} Amiga Intuition Based Benchmarks @{b}EXAMPLE:@{ub} GNU C Compiler @{b}NOTES:@{ub} If the @{"name" link .name} is not an abbreviation then omit the @{"fullname." link .fullname.} No sense in giving the name twice! @ENDNODE @NODE .installsize "Product-Info field: .installsize" @{LINDENT 3} @{fg shine}@{b}@{u}.installsize:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Indicate the minimum and maximum sizes of the executable as it is installed. The minimum size should give an indication of how much diskspace is required for a minimal installation (perhaps lacking help files and miscellaneous tools) while the maximum size should indicate the absolutely highest amount of diskspace required by the program. @{b}FORMAT:@{ub} 1 or more lines; Only the first line has a fixed format, the rest are free-form. See examples. Always indicate the number scales with a capital K (for kilobyte) or M (for megabyte) @{b}EXAMPLE:@{ub} 220K - 2M Most of the database files can be kept on floppy disks, so valuable harddisk space is not wasted. @{b}EXAMPLE:@{ub} 18K @{b}EXAMPLE:@{ub} 38K - 500K Lots of documentation and example scripts make up the bulk of the installation. @ENDNODE @NODE .keywords "Product-Info field: .keywords" @{LINDENT 3} @{fg shine}@{b}@{u}.keywords:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .locale "Product-Info field: .locale" @{LINDENT 3} @{fg shine}@{b}@{u}.locale:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .name "Product-Info field: .name" @{LINDENT 3} @{fg shine}@{b}@{u}.name:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} The program's name @{b}FORMAT:@{ub} 1 line only @{b}EXAMPLE:@{ub} KingFisher @{b}EXAMPLE:@{ub} HomeBase VI @{b}EXAMPLE:@{ub} AIBB @{b}EXAMPLE:@{ub} gcc @ENDNODE @NODE .phone "Product-Info field: .phone" @{LINDENT 3} @{fg shine}@{b}@{u}.phone:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} @{b}FORMAT:@{ub} @{b}NOTES:@{ub} @ENDNODE @NODE .price "Product-Info field: .price" @{LINDENT 3} @{fg shine}@{b}@{u}.price:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describes the cost of this program to the user. @{b}FORMAT:@{ub} Any number of lines, treated as one line. @{b}EXAMPLE:@{ub} $50(US), DM75. @{b}NOTES:@{ub} In order to make this field more useful, it is STRONGLY recommended that the FIRST currency listed is United States Dollars as shown in the EXAMPLE above. This allows a search to be limited to a common price base. If you charge no money for this program, omit this field! @ENDNODE @NODE .reference "Product-Info field: .reference" @{LINDENT 3} @{fg shine}@{b}@{u}.reference:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Full path to where this program's files are stored, as well as the version that is stored there. @{b}FORMAT:@{ub} 2 lines per reference: the first line specifies the full path (with trailing slash) and the second line, the version. @{b}NOTES:@{ub} Multiple such fields may be provided to reference previous versions of this program, as well as other programs that might be of interest. The versions should be listed in reverse chronological order and SHOULD include the CURRENT entry. Please note that it is VERY VERY VERY important that you specify the CORRECT PATH! Without a correct path, this entry will be nearly useless! SPECIFY THE PATH WITH A NEW SUBMISSION ONLY IF YOU KNOW WHERE IT IS STORED; NEW SUBMISSIONS WILL HAVE A PATH ASSIGNED HERE AUTOMATICALLY. YOU SHOULD PROVIDE THE PROPER PATHS TO KNOWN AND EXISTING SOFTWARE. @{b}EXAMPLE:@{ub} FishROM-0002:Productivity/Databases/HomeBase VI/ 417.0 FishROM-0001:Productivity/Databases/HomeBase VI/ 415.12 @ENDNODE @NODE .requirements "Product-Info field: .requirements" @{LINDENT 3} @{fg shine}@{b}@{u}.requirements:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} List requirements for your program. These should give the reader enough information to determine if the software will run on his/her system or not. Be sure to specify operating system versions, (hard)disk space requirements, etc. If your program requires any external libraries that are not part of the system software, it would be nice to list them here and comment on whether or not they are included in the archive. If your program is known to run on every existing (Amiga) platform, state this in this field! @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more info. @{b}EXAMPLE:@{ub} 68020, 68030, or 68040 CPU; 3M free RAM; 18M disk space; at least 640x480 display capabilities! @{b}EXAMPLE:@{ub} Requires WB2.1 (V38) @{b}EXAMPLE:@{ub} Requires 1024x768 (or larger) display capability. @{b}EXAMPLE:@{ub} Works only with 4096-channel, 230db BLAZETHUNDER Audio board. @{b}EXAMPLE:@{ub} Requires MUI (MagicUserInterface) version 5. @ENDNODE @NODE .restrictions "Product-Info field: .restrictions" @{LINDENT 3} @{fg shine}@{b}@{u}.restrictions:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} List restrictions placed upon this program. These should indicate in which way this program has been made dysfunctional (for demo purposes), problems (bugs) known to exist with this program, or any other thing that lets the user know that this program, as seen in this distribution, may not fully satisfy the user in some form. @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more info. @{b}EXAMPLE:@{ub} Demo version has SAVE and PRINT options disabled. @{b}EXAMPLE:@{ub} The ReadOperatorsMind command fails to work with CDTV units. Incompatible with the Discus Ejector utility. @{b}EXAMPLE:@{ub} Crashes if iconified while loading a sample or image larger than 64K. @{b}EXAMPLE:@{ub} Requires a PAL display. @{b}EXAMPLE:@{ub} The program is in German but the documentation offers translations into English and Swahili on a menu-by-menu and gadget-by-gadget basis. @{b}NOTES:@{ub} Do NOT use this field for things like "won't work with KS 1.3" or "won't run with less than 2 Megs of RAM." @ENDNODE @NODE .run "Product-Info field: .run" @{LINDENT 3} @{fg shine}@{b}@{u}.run:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Specifies how to start the program. @{b}FORMAT:@{ub} visible=type,command Where 'type' is either WB or CLI to indicate the required startup environment. @{b}EXAMPLE:@{ub} HomeBase VI=WB,HomeBase VI HomeBase VI=CLI,ExecuteMe.HB6 HomeBase VI Fixer=CLI,ExecuteMe.HB6Fixer @{b}EXAMPLE:@{ub} FishTub=WB,ExecuteMe @{b}NOTES:@{ub} KingFisher requires that this entry strictly follows the above format. The user is shown all text up to the first equal sign (the 'visible' portion.) The 'type' portion must be terminated with a comma (,) and following it will be the command to be executed. Selecting it will either invoke the program from the Workbench (invoking it as if double clicked on its icon (if the .info file exists), or execute the indicated shell command line as if it has been typed at an open console window. @ENDNODE @NODE .short "Product-Info field: .short" @{LINDENT 3} @{fg shine}@{b}@{u}.short:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} A one-line description, preferrably not exceeding 40 characters in length. This description is to give a single-glance insight into the program's purpose. @{b}FORMAT:@{ub} 1 line only. @{b}EXAMPLE:@{ub} Software catalog/search/maintenance tool, multi-user. @ENDNODE @NODE .source "Product-Info field: .source" @{LINDENT 3} @{fg shine}@{b}@{u}.source:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Describe what source code is available with this program. If source code is not available then omit this field. The @{"construction" link .construction} field often helps further identify the type of source if you omit details here. How large is the source? @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more information. @{b}EXAMPLE:@{ub} SAS/C,Manx,DICE source (750K) available for $15 @{b}EXAMPLE:@{ub} Oberon source included. 85K @{b}EXAMPLE:@{ub} Limited C source (15K) included. @{b}EXAMPLE:@{ub} All source plus custom libraries, included: 12MB @ENDNODE @NODE .stored-in "Product-Info field: .stored-in" @{LINDENT 3} @{fg shine}@{b}@{u}.stored-in:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} Specifies where and especially HOW the application is stored. This field should specify EITHER the name of a directory (ending with a : or a /) OR the name of a file (one that does NOT end with : or /) @{b}FORMAT:@{ub} 1 or more lines. @{b}EXAMPLE:@{ub} FF1000:Disks701-1000/Disks941-960/Disk950/Enforcer/ FF1000:BBS/Disks501-1000/Disks941-960/Disk950/Enforcer.lha @{b}NOTES:@{ub} It is up to the particular application to decide how to handle this information. If the extension on the file is .lha, .lzh, .Z, .zoo, .pak, .zip, etc. then you could, for example, call upon the archiver of choice to unpack the application into a temporary directory and let the user run the program or list the files, or whatever. @ENDNODE @NODE .submittal "Product-Info field: .submittal" @{LINDENT 3} @{fg shine}@{b}@{u}.submittal:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Identifies who submitted the program to Fred or else how this program came to be on the reference disk. @{b}FORMAT:@{ub} Free form; usually one line. @{b}EXAMPLE:@{ub} Submitted on disk directly by the author. @{b}EXAMPLE:@{ub} Downloaded from wuarchive.wustl.edu in pub/aminet/util/misc @ENDNODE @NODE .tested "Product-Info field: .tested" @{LINDENT 3} @{fg shine}@{b}@{u}.tested:@{uu}@{ub}@{fg text} @{fg fill}<<>>@{fg text} @{b}PURPOSE:@{ub} Give an indication of which configurations have served as test environments. @{b}FORMAT:@{ub} Free form; see @{"description" link .description} for more information. @{b}EXAMPLE:@{ub} A500(512K Chip, 0K Fast, 1 Floppy), A2000(1M Chip, 2M Fast, 40M HD, 1 Floppy); not tested on 68020+ CPUs. @{b}EXAMPLE:@{ub} A1000, A500, A600, A2000, A2000/30, A3000, A1200, A4000/30, A4000/40 with various amounts of Chip and Fast RAM, with and without MMU or FPU. Found to be free of Enforcer hits and able to work with virtual memory products; compatible with Retina, EGS/Spectrum, and Picasso software. Also tested under V33 through V40 system software. @ENDNODE @NODE .type "Product-Info field: .type" @{LINDENT 3} @{fg shine}@{b}@{u}.type:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} A keyword that describes the nature of the program @{b}FORMAT:@{ub} Preferrably a single word or two. @{b}EXAMPLE:@{ub} Database @{b}EXAMPLE:@{ub} Spreadsheet @{b}EXAMPLE:@{ub} Animation Player @{b}EXAMPLE:@{ub} Animation Tools @{b}EXAMPLE:@{ub} Communications @{b}EXAMPLE:@{ub} Display Commodity @{b}EXAMPLE:@{ub} Mouse Commodity @{b}NOTES:@{ub} Avoid abbreviations. Refer to the list below for suggestions. EXAMPLES OF "TYPE" WORDS Action Game Animation Animation Player Animation Tool Archiver CLI Tool Communications Compiler Compression Database Disk Tool Display Commodity Drawing Image Conversion Image Processing Library Mouse Commodity Music Composition OS Utility Painting Picture Printing Sound Analysis Sound Editing Sound Playing Spreadsheet Strategy Game Text Text Editing Text Viewer Thinking Game Word Processing Workbench Tool @ENDNODE @NODE .version "Product-Info field: .version" @{LINDENT 3} @{fg shine}@{b}@{u}.version:@{uu}@{ub}@{fg text} @{b}PURPOSE:@{ub} The program's version number @{b}FORMAT:@{ub} MAJOR.MINOR 1 line only @{b}EXAMPLE:@{ub} 37.100 @{b}NOTES:@{ub} Please note that the Commodore guidelines specify that the number after the period is NOT a FRACTION but rather a WHOLE NUMBER! Thus, the following is a valid progression: 37.1 37.17 37.39 37.100 37.170 The following are all vastly different versions: 37.1 37.10 37.100 37.1000 @{b}NOTES:@{ub} The format given for this field is really more of a SUGGESTION rather than a RULE. There is no reason why you can't store "Today's Version" or "v940205" instead of 18.173. In an ideal world everyone would use Commodore guidelines, but there are enough exceptions. @ENDNODE