##Task
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.

= F.2. Coding guidelines =

## Valid states: "Not started", "In progress" and "Finished"
'''State:''' Deprecated

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''Time used:''' 0 md.

/!\ This page has been deprecated. The task pages D.2.4 to D.2.7 now covers this task.


== Description ==

## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.

Write coding guidelines, such as maximum line width, position of line breaks and so on.

##== Sub tasks ==

## . [:TaskX.Y.Z: Add sub task link 1 here]
## . [:TaskX.Y.Z: Add sub task link 2 here]
## .         ..[[BR]]
## .         ..[[BR]]
## .         ..
## . [:TaskX.Y.Z: Add sub task link N here]

##== Documentation ==

## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page.
## This should be a proper default, however, it may be changed.
 
## * [:TaskF.2AnalysisDocument: Analysis Document]
## * [:TaskF.2DesignDocument: Design Document]
## * [:TaskF.2SystemMaintenanceDocument: System Set-up and Maintenance Document]

== Parent task ==
 * [[TaskF]]

== Progress history ==

## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.

=== 2007-09-13 ===

Regarding [[Guidelines]] the pages CodeStyle, [[QA Guidelines]] and [[i18n]] has been generated and is considered finished within the scope of this task.

On the question on [[Tools]] the page [[Tools]] has been set up containing a list and description of the tools we chose to use.

''Summary'': CodeStyle should not contain any big surprises, with the possible exception of the {{{// FIXME:}}}- comment. QA is programmer-driven and annotation-enriched: The programmer is responsible for calling for reviews. Internationalisation is done with Sun's framework, plus a custom wrapper. We use Jdk1.5, SVN, Idea > 6.0.5, Continuum build server, and Ant 1.7 for build scripts.