DRF, Download, Read & Feel

Download, Read and Flow/Feel, or DRF is a tag and workmethod for idea-progressing and maintaining small projects. Mostly used for early software-development, coding, tweaking, modding or hacking.

The owner of a DRF package, named hereafter masteruser, starts a DRF when there is need for a quickstart project. The masteruser needs a quick way to log the project and when in need can monitor or present the progress of this project. The project than can easily be made opensource to welcome assistance or any other kind of help. The purpose of the DRF working method is to make quick, small but fully documantated project packages, approachable for anyone. For the masteruser the DRF label becomes a easy way for logging and sharing projects with a sustainable coverage over all kinds of mediums. For guestusers, the DRF label is startpoint to find, learn and help with projects of any kind.

Starting a DRF DRF0, short for Download, Read & Followup

The start of DRF project is a DRF0 package, the 0 in DRF0 will count on with newer versionnumbers as work on the project progresses. The version number is changed by choice of the masteruser. Example: DRF0, DRF1, DRF2 etc. The DRF package in this stage always consists out of non-executable files. The package may be compressed with zip or rar. Acces and security of the package can be maintained this way.

In the beginning, the package only contains files with three different names, corresponding to the three steps in the tag DRF. More files with the same name but containing other data, are numbered. Example: Droid.html, Droid1.html

1-Droid files, these files contain code, target or idea. In other words the project itself.

2-Rope files, these files contains all the info, guidance, progress, logdata, correspondance and all filenames included in the current DRF version.

The third filename is not always included at this stage. These files will be added as the DRF0 package progresses.

3-Flow files, these are all media files of common type. With the only purpose to add a presentation and show the progress. Screenshots are the most common Flow-files. The presentation may advance to become the first pilot or a mockup.

Other filenames: Any other filenames, are files needing the original filename to be used with the guidance of the Rope-files. Also tekstfiles with customized filetype labels can be part of them. These files are save to open with any teksteditor when filesize is under 1Mb. But still all files belong to one of the three DRF categories.

The final stage of a DRF Project. DRF, short for Download, Read and Feel.

When the DRF project reaches it's goal, the DRF0 package will drop the version number. The DRF is closed by its original owner. Now the DRF is a completed DRF. The next stage will stay out, because the DRF does suffice it's purpose or will further progress as part of a bigger project or grow to a bigger DRF unworthy status.

The completed DRF always includes the 3 components of DRF. -Droid (with corresponding files when needed) -Rope(including guidance, contactinfo, table of filenames in the DRF package) -Flow (mediafiles) and the Fire-file (mockup, test, demo, the final presentation) In this stage the package may be executable in many different ways, but always with low-maintainability with commonly used formats.

DRF package and guest users DRF consists of a package of files, with the needed code, instructions, guide and ultimately, the presentation file (examp. Fire.pdf). Everything needed for the project should be included in the DRF package. The Rope-file contains the table of the included filenames and guidance. All new files or changes made by a guestuser are saved as a new file with the corresponding filename within the three categories, plus a new 3-letter string between the category and the filetype label.

Example, Eva is guestuser: Eva edites Droid.html, she will save her edited file as DroidEVA.html, advancing becomes DroidEVA1.html etc. If there is a second Droid-file, like Droid1.html, the edited file of Eva is saved as Droid1EVA.html and so on. New files are counted after its category; Eva makes a new Droidfile, the last droidfile was droid 1, new file is saved as Droid2EVA.html. When in case more files belong to one Rope file the file gets a letter: Rope1.txt, Droid1.html, Flow1.jpg and Flow1a.png belong together. Suggestions, questions, help, info or guides become RopeEVA.txt, RopeEVA1.txt etc. The three categories are always linked to eachother with these versionnumbers. Example: Rope3EVA5.txt is all info on Droid3EVA5.html. Media files on this file is Flow3EVA5.jpg. In this way, all files have there corresponding info- and mediafiles. always corresponding to the belonging file, in this case RopeEVA1.txt belongs to DroidEVA1.html. When making a new file, example Fire-files are files only created by the masteruser, these files only get edited by the masteruser.

How files belong together to one version of edit etc: Test.DRF0

 Droid.php
 Rope.txt
 Flow.jpg
 Flowa.png
 Flowb.avi
 Droid1.php
 Rope1.txt
 Flow1.wav
 Droid1EVA.php
 Flow1aEVA.mp3
 Flow1aEVA1.mp3