Changes between Version 17 and Version 18 of DevelopersCorner


Ignore:
Timestamp:
Mar 8, 2008, 7:48:42 AM (16 years ago)
Author:
pagameba
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DevelopersCorner

    v17 v18  
    2727 * [wiki:CreatingPatches Using SVN to create patches]
    2828
    29 === Using SVN ===
     29== Coding Standards ==
    3030
     31Fusion code is written to certain [wiki:CodingStandards coding standards] based on a combination of community best practice, readability and what feels comfortable.  If you are writing code to contribute to Fusion, please make sure you read the [wiki:CodingStandards coding standards] page before submitting your code.
    3132
     33== Documentation ==
    3234
    33 To check out a copy of '''trunk''', a branch, a tagged version, or a sandbox, you need to know the ''URL'' and use {{{svn checkout <url>}}}.  For instance:
    34 
    35  * {{{svn co http://svn.osgeo.org/fusion/trunk}}} - check out trunk
    36  * {{{svn co http://svn.osgeo.org/fusion/branches/fusion-1.0}}} - check out the branch for version 1.0
    37  * {{{svn co http://svn.osgeo.org/fusion/tags/fusion-1.0.0}}} - check out the 1.0.0 released version
    38  * {{{svn co http://svn.osgeo.org/fusion/sandbox/pagameba}}} - check out pagameba's sandbox
    39 
    40 Once you have a checked out copy, this is called a working copy.  To update a working copy to the latest version, you use the ''update'' command with no arguments:
    41 
    42  * {{{svn update}}}
    43 
    44 To move the working copy to a specific revision number, you can add the ''revision'' parameter:
    45 
    46  * {{{svn update -r <revision>}}}
    47 
    48 To see if you have changes in your working copy against the current revision:
    49 
    50  * {{{svn status}}}
    51 
    52 To see the differences between your working copy and the current revision:
    53 
    54  * {{{svn diff}}}
    55  * {{{svn diff > diff.patch}}} redirects the output to a file that is suitable for using with the {{{patch}}} command
     35Fusion user documentation is maintained primarily in in the [wiki:Documentation] section of this wiki.  The API documentation is maintained in the Fusion code using [http://www.naturaldocs.org/ NaturalDocs].  See the [wiki:DocumentationStandards documentation standards page] for details on documenting your code.
    5636
    5737== The Build Process ==
    5838
    59 === Creating a binary build ===
     39The Fusion build process is used to create release packages.  The Fusion build process uses:
    6040
     41 * the [http://ant.apache.org/ ANT] build system to create redistributable packages,
     42 * the [http://javascript.crockford.com/jsmin.html jsmin] tool to create compressed versions of the javascript files, and
     43 * the [http://www.naturaldocs.org/ NaturalDocs] package for automating the generation of API documentation
     44
     45See the [wiki:ANTBuildSystem ANT Build System] page for details on running ANT to create release packages.
     46