Changes between Version 73 and Version 74 of Developers/Dev Process


Ignore:
Timestamp:
2016-07-02T01:13:39+02:00 (4 years ago)
Author:
nicolasmartin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Dev Process

    v73 v74  
    33 
    44== Help == 
    5 A wiki page associated with a give action should be created in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this template.[[BR]] 
    6 For the creation of the page of the editing of the template itself (Trac links for !ticket & source), '''it is mandatory to visualize it in 'textarea' view''' and not in 'wysiwyg' view as it will alter the interpretation of the Trac processors {{{#!th ... }}} or {{{#!td ... }}} in the complex tables.[[BR]] 
    7 To avoid it and keep a preview, you can enable the side-by-side edition (tick box at top right of the editing frame). It will part your screen with the editing view on the left and the automatic preview on the right to control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner. 
     5A wiki page associated with a given action should be created in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this template. '''Each editor (PI/Previewer/Reviewer) complete its section inside the form fields and save its modifications by clicking on the 'Save' button at the end of the section''' (editing log will be updated just above it).[[BR]] 
    86 
    9 Apart form this, '''each editor complete its section inside the form fields and save its modifications by clicking on the 'Save' button at the end of the section''', the date and the author of the last edition will be updated above it.[[BR]] 
    10 There is absolutely no risk to make any operation on the wiki page itself and especially delete last version or submit a new one. The content of the form fields are recorded and singled out by the URL of the wiki page, the form context ('Abstract'/'Preview'/'Tests'/'Review') and subcontext (fields name).[[BR]] 
    11 From that, you can customize it while editing within the !TracForm container `{{{#!TracForm ... }}}`. If necessary, you can copy the entire form (add a number `_[0-9]` to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page. 
    12  
    13 This is the color code for the fulfilment of this form: 
    14 {{{#!td style='background:lightgrey' 
    15 PI(S) 
     7This is the '''color code''' for the fulfilment of this form: 
     8{{{#!td font-style='bold' style='background:lightgrey' 
     9'''PI(S)''' 
    1610}}} 
    1711{{{#!td style='background:lightblue' 
    18 Previewer(s) 
     12'''Previewer(s)''' 
    1913}}} 
    2014{{{#!td style='background:lightgreen' 
    21 Reviewer(s) 
     15'''Reviewer(s)''' 
    2216}}} 
     17 
     18'''There is absolutely no risk for all form content to make any modification in the wiki page as long as you edit out of `{{{TracForm ... }}}` processor'''. The data of a form field is recorded in a different database from the wiki page, so you can delete a version or submit a new one without danger.[[BR]] 
     19 
     20'''For the Trac links to associated !ticket & development branch, it is mandatory to edit the page in `textarea` view'''. The `wysiwyg` view will alter the interpretation of the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}` in the table.[[BR]] 
     21''To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame). It will part your screen with the editing view on the left and the automatic preview on the right so you can control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner.'' 
    2322 
    2423----