Changes between Version 84 and Version 85 of TracFormsPlugin
- Timestamp:
- Oct 19, 2015, 5:22:22 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFormsPlugin
v84 v85 5 5 == Description 6 6 7 This plugin allows you to add forms anywhere where there is a field with Trac wiki syntax. This is meant to supersede the previously limited-scope ChecklistPlugin. 7 This plugin allows you to add forms anywhere where there is a field with Trac wiki syntax. This is meant to supersede the previously limited-scope ChecklistPlugin. 8 8 9 WikiFormsPlugin aims at providing even more flexibility with a sightly more complex wiki markup incompatible to that of !TracFormsPlugin.9 The similar WikiFormsPlugin aims at providing even more flexibility with a sightly more complex wiki markup incompatible with that of this plugin. 10 10 Additional features from this plugin have been requested here too (see #8715). 11 11 … … 18 18 {{{ 19 19 20 == Laundry list example ==20 == Laundry list example 21 21 22 22 {{{ 23 23 #!TracForm 24 24 # 25 # An example of a TracForm. 25 # An example of a TracForm. The first lines can be commentary or #! commands. 26 26 # 27 27 #! track_fields … … 50 50 }}} 51 51 52 Note that the form is blank and you can play with the results again. This is because the default context for the form is the page URL itself! 52 Note that the form is blank and you can play with the results again. This is because the default context for the form is the page URL itself! That means that as long as a form is included on a different page (and the default context is not overridden), then each page including gets its '''own''' version of the form's results. This works particularly well with !PageTemplates. 53 53 54 Now, for more fun, do the same thing in a ticket. Once submitted, every ticket including the template will contain it's own checklist. 54 Now, for more fun, do the same thing in a ticket. Once submitted, every ticket including the template will contain it's own checklist. One obvious use for this is when creating a svn commit checklist. Simply put the checklist in the appropriate wiki location, create tickets that include the location, and voila, instant commit step-by-step. Once enough of the form becomes exposed, we should be able to work this into the workflow too (no resolving before at least paying lip service to the checklist). 55 55 56 56 There is much more planned for this plugin than simply checklists. See [wiki:TracFormsPlugin/Docs] for more information on the various ways to use this tool. … … 61 61 [query:status=new&status=assigned&status=!closed&component=TracFormsPlugin&order=priority here]. 62 62 63 If you have any issues not covered by the existing tickets (including closed ones), create a63 If you have any issues, create a 64 64 [/newticket?component=TracFormsPlugin new ticket]. 65 65 … … 98 98 === Method 1: Lay an egg 99 99 100 From here, you can do one of two things. 100 From here, you can do one of two things. The first is building an egg to drop into your project's plugins directory or your master project's plugins directory (replace or define $TRACENV_DIR with your project's base directory): 101 101 102 102 {{{#!sh … … 136 136 FORM_EDIT_VAL:: enable submission of form content changes - these users will be able to see and use 'Update Form' buttons 137 137 FORM_RESET:: enable incremental and full form version clean-up by using additional action buttons on form details pages 138 FORM_ADMIN:: justinherits all previous permissions, nothing more yet138 FORM_ADMIN:: inherits all previous permissions, nothing more yet 139 139 140 140 === About i18n/l10n support
