Ignore:
Timestamp:
1 Feb 2010, 22:11:30 (15 years ago)
Author:
uli
Message:

Fix package names and svn download path.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.sirp/trunk/src/waeup/sirp/doc/developernotes.txt

    r4789 r4978  
    22***************
    33
    4 How to setup a developer instance of the WAeUP SRP, handle tests, docs
     4How to setup a developer instance of the WAeUP SIRP, handle tests, docs
    55etc.
    66
    7 The new WAeUP SRP is based on `Grok <http://grok.zope.org/>`_.
     7The new WAeUP SIRP is based on `Grok <http://grok.zope.org/>`_.
    88
    99Installing a developer copy
     
    1515--------------------
    1616
    17 To create a working copy of the WAeUP SRP we recommend use of
     17To create a working copy of the WAeUP SIRP we recommend use of
    1818`virtualenv`. You, however, need also some basic libraries, a C
    1919compiler and some things more.
     
    127127In the sandbox (or anywhere else) we now create our real working
    128128environment. To do this, we change to the sandbox and checkout the
    129 sources of the WAeUP SRP from the subversion server::
     129sources of the WAeUP SIRP from the subversion server::
    130130
    131131  $ cd mysandbox/
    132   $ svn co https://svn.waeup.org/repos/waeup/tunk waeup-trunk
     132  $ svn co https://svn.waeup.org/repos/main/waeup.sirp/trunk waeup-trunk
    133133
    134134where ``waeup-trunk`` is only a name we've chosen here to make clear
     
    194194=============
    195195
    196 With the :mod:`waeup` package we try to reach high standards in both,
    197 documentation and testing.
    198 
    199 :mod:`waeup` makes extensive use of doctests, which this way also
     196With the :mod:`waeup.sirp` package we try to reach high standards in
     197both, documentation and testing.
     198
     199:mod:`waeup.sirp` makes extensive use of doctests, which this way also
    200200become both: executable (i.e. testable) examples and documentation.
    201201
     
    206206documentation generator to generate the docs as HTML pages.
    207207
    208 The documentation of the :mod:`waeup` project can easily be created
    209 doing::
     208The documentation of the :mod:`waeup.sirp` project can easily be
     209created doing::
    210210
    211211  $ bin/waeupdocs
    212212
    213213This will create a tree of HTML pages in
    214 ``parts/waeupdocs/waeup/build/waeup/`` which you can for instance
    215 browse by pointing your browser to this location.
     214``parts/waeupdocs/waeup.sirp/build/waeup.sirp/`` which you can for
     215instance browse by pointing your browser to this location.
    216216
    217217An 'official' place in internet for the whole docs is about to come
     
    223223
    224224means explaining to other developers what your code does and test it
    225 at the same time. See the many .txt files in the :mod:`waeup` package
    226 for examples.
     225at the same time. See the many .txt files in the :mod:`waeup.sirp`
     226package for examples.
    227227
    228228
     
    230230=======
    231231
    232 Tests are most important to the reliability of the :mod:`waeup`
     232Tests are most important to the reliability of the :mod:`waeup.sirp`
    233233package. We don't tell someone that our code works, if we cannot prove
    234234it. And we prove it by testing.
     
    246246  $ bin/test -c
    247247
    248 We have many tests in the :mod:`waeup` package so that sometimes you
    249 only want the functional *or* the unit tests to run. This can be done
    250 like this::
     248We have many tests in the :mod:`waeup.sirp` package so that sometimes
     249you only want the functional *or* the unit tests to run. This can be
     250done like this::
    251251
    252252  $ bin/test -c -u
Note: See TracChangeset for help on using the changeset viewer.