/
DEVELOPERS
99 lines (71 loc) · 3.46 KB
/
DEVELOPERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
DEVELOPER INFO
--------------
phpPgAdmin is Open Source, so you're invited to contribute to it.
Many great features have been written by other people and you too
can help to make phpPgAdmin a useful tool.
phpPgAdmin 3.0 has its roots in the phpPgAdmin 2.4 software. A complete
rewrite was necessary to support PostgreSQL 7.3 and to address problems
in the phpPgAdmin 2.4 codebase.
If you're planning to contribute source, please read the following
information:
The following method is preferred for new developers:
- fetch the current CVS tree over anonymous CVS:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/phppgadmin login
[Password: ] simply press the Enter key!
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/phppgadmin co -d phpPgAdmin webdb
[This will create a new sub-directory named phpPgAdmin]
- Add your stuff
- Send us the file(s) you've modified or send us a patch (preferred). To generate a patch, do this
in your 'phpPgAdmin' directory:
cvs diff -c > file.txt
Then, just send us the file.txt
Please note submitting code is considered a transfer of copyright to the phpPgAdmin project.
Only project developers can access the CVS tree via ssh and SSH1 must
be installed on your client machine.
export CVS_RSH=ssh
login once with ssh to developername@cvs.phppgadmin.sourceforge.net to create required
user directories on the server.
cvs -z3 -d:ext:developername@cvs.sourceforge.net:/cvsroot/phppgadmin co -d phpPgAdmin webdb
Write access to the CVS tree is granted only to developers who have already
contributed something useful to phpPgAdmin. If you're interested in that,
please contact us.
TIPS FOR DEVELOPERS
-------------------
When you submit code to phpPgAdmin, we do expect it to adhere to the existing
coding standards in the source. So, instead of using your personal favourite
code layout style, please format it to look like surrounding code.
Test your code properly! Say you are developing a feature to create domains.
Try naming your domain all of the following:
* "
* '
* \
* words with spaces
* <br><br><br>
If you are adding a new class function, be sure to use the "clean",
"fieldClean", "arrayClean" and "fieldArrayClean" functions to properly escape
odd characters in user input. Examine existing functions that do similar
things to yours to get yours right.
When writing data to the display, you should always urlencode() variables in
HREFs and htmlspecialchars() variables in forms.
COMMON VARIABLES
----------------
$data - A data connection to the template1 database.
$localData - A data connection to the current database.
$misc - Contains miscellaneous functions. eg. printing headers and footers, etc.
$lang - Global array containing translated strings. The strings in this array have already
been converted to HTML, so you should not htmlspecialchars() them.
$conf - Global array of configuration options.
WORKING WITH RECORDSETS
-----------------------
phpPgAdmin uses the ADODB database library for all its database access. We have
also written our own wrapper around the ADODB library to make it more object
oriented (ADODB_base.pclass).
This is the general form for looping over a recordset:
$rs = &$class->getResults();
if (is_object($rs) && $rs->recordCount() > 0) {
while (!$rs->EOF) {
echo $rs->f['field'];
$rs->moveNext();
}
}
else echo "No results.";