| description |
I want a web page where all kinds of therapy can be given by mail or live video conference. Interactive calender where registered therapist can control their patients bookings. This is the main things but further discussion will be made when we are in contact with each other. The budget will be discussed when i bring my whole idea. show/hide addendum
|
|
1. Code must be developed and demonstrated on your own linux web server, using my input files and producing specified output files.
2. Code should be concise; no repeated blocks, no files read more than once if not necessary, etc.
3. Copyright will be owned by me; I will credit you in the source code and/or on my webpage.
4. You should strive to use open source components as appropriate, choosing components based on popularity and reliability, amount of active development, etc. You must list all open source or other components used for my project, and verify that we have rights to later use them commercially if I choose.
5. Once I approve the output, send me a zipfile containing and source code, and a Makefile with these components:
* a comment on the purpose of each file.
* a comment with a pointer to your webpage which demonstrates your successful use of the program.
* a target of "run" which runs the program with appropriate input and output files specified.
* a target of "clean" which removes all output and temporary files.
* any appropriate "install-xxx" targets to download and install any required components from the net.
6. I will then the code on my linux server using your Makefile; and must verify that it produces the correct output on my server.
7. For C-like programming languages (Java, JavaScript, Perl, PHP, Ruby, etc.), please use the following conventions:
a) Use a programmer's editor that does automatic formatting, e.g., emacs.
b) Keep all lines less than 78 characters long. (If you absolutely need to have a long line, consider putting a blank line above and below it, to make it easier to read.)
c) Use two spaces for indentation level. (Wider indents would make more lines wrap.)
d) Make all inline comments start in the same column when possible. I.e., in emacs try M-; to run indent-for-comment.
e) Use a 65-dash comment to separate sections, e.g., for Perl:
# -----------------------------------------------------------------
# subroutines/functions/methods:
f) Most subroutines should be less than about 50 lines of code.
g) Usually put a space before any open parens, and after every comma and semi-colon, and on either side of built-in operators like the = sign.
h) Do not put two statements on one line.
i) Open brace at end of line like this:
if condition {
action();
}
j) Always follow an if/for/while clause with {} to wrap the actions, even if there is only one statement as the action.
|
