Project

General

Profile

Using Docblocks for quality code documentation » History » Version 26

Simon Hodgkiss, 01/22/2010 02:52 PM

1 1 Simon Hodgkiss
h1. Using Docblocks for quality code documentation
2 2 Simon Hodgkiss
3 22 Simon Hodgkiss
h2. Important information to developers
4 1 Simon Hodgkiss
5 26 Simon Hodgkiss
6 25 Simon Hodgkiss
1. The top Docblock should stay the same in all files.
7 1 Simon Hodgkiss
8 25 Simon Hodgkiss
2. The top copyright is to stay the same.
9 23 Simon Hodgkiss
10 25 Simon Hodgkiss
3. The minimum Docblock you should use has to have at least: A Description, @package    VirtueMart and an @author.
11 18 Simon Hodgkiss
12 17 Simon Hodgkiss
13 15 Simon Hodgkiss
However you make add the @copyright into the docblock of any of code your wish to add additional copyright to.
14 12 Simon Hodgkiss
15 13 Simon Hodgkiss
16 8 Simon Hodgkiss
17 6 Simon Hodgkiss
The way in which each file should be documented has changed slightly. You may have already seen some changes to a few of the files already. Here you will find all the references you will need to keep your files to out new Docblock documentation. 
18 4 Simon Hodgkiss
19
I have provided you with two files for each type one which has comments on how the document tags work and which should be used.
20
The other is a blank file which has the basic template for you to drop any code into.
21 7 Simon Hodgkiss
22
If you do not require all the @tags when documenting your code feel free to take them out.
23 11 Simon Hodgkiss
24
25
26
27
28
29
30
31
32
33
...