Changes between Version 87 and Version 88 of TracFormsPlugin


Ignore:
Timestamp:
Nov 20, 2015, 11:47:34 AM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracFormsPlugin

    v87 v88  
    1414Also see the online [wiki:TracFormsPlugin/Tutorial tutorial] or the [wiki:TracFormsPlugin/Docs documentation] (docs still in need of some corrections and updates to 0.4).
    1515
    16 Let's start by looking at a simple laundry list. This list will be automatically bound to whatever page it appears in by default (this can be configured). Once the plugin is installed, simply edit a new wiki resource called `Sandbox/LaundryList` and chuck this in:
     16Let's start by looking at a simple laundry list. This list will be automatically bound to whatever page it appears in by default (this can be configured). Once the plugin is installed, simply edit a new wiki resource called `Sandbox/LaundryList` and add this:
    1717
    1818{{{
    … …  
    3636}}}
    3737
    38 Once saved, you should get something looking like this:
     38Once saved, you should see something like this:
    3939
    4040[[Image(LaundryList.jpg)]]
    4141
    42 From here, you can check some things and click "Submit Query" you'll see the fields change. After a few clicks it might look like this:
     42From here, you can click "Submit Query" and you will see the fields change. After a few clicks it might look like this:
    4343
    4444[[Image(LaundryList2.jpg)]]
    … …  
    5252Note 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.
    5353
    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).
     54Now, for more fun, do the same thing in a ticket. Once submitted, every ticket including the template will contain its 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).
    5555
    5656There 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.
    … …  
    6868== Download and Source
    6969
    70 || Stable Version || [source:tracformsplugin/tags/tracforms-0.4.1] || [download:tracformsplugin/tags/tracforms-0.4.1 download] || [http://trac-hacks.org/svn/tracformsplugin/tags/tracforms-0.4.1 subversion]
    71 || Under Development || [source:tracformsplugin/trunk] || [download:tracformsplugin/trunk download] || [http://trac-hacks.org/svn/tracformsplugin/trunk subversion]
     70|| Stable Version || [source:tracformsplugin/tags/tracforms-0.4.1] || [export:tracformsplugin/tags/tracforms-0.4.1 download] || [/svn/tracformsplugin/tags/tracforms-0.4.1 subversion]
     71|| Under Development || [source:tracformsplugin/trunk] || [export:tracformsplugin/trunk download] || [/svn/tracformsplugin/trunk subversion]
    7272
    7373The current stable version is usable with Python 2.6; an older Python requires [http://simplejson.github.com/simplejson/ simplejson] to be installed.
    7474
    75 Revision [10011] and above requires some dedicated permissions assigned to use new (search) as well as known !TracForms features ('Update Form' button).
     75Revision [10011] and above requires some dedicated permissions assigned to use new features (such as Search) as well as known !TracForms features (such as the 'Update Form' button).
    7676
    77 You can also download the entire project [download:tracformsplugin here], or checkout a copy using [http://trac-hacks.org/svn/tracformsplugin subversion].
     77You can also download the entire project [export:tracformsplugin here], or checkout a copy using [/svn/tracformsplugin Subversion].
    7878
    7979== Installation
    … …  
    131131=== Grant user persmissions
    132132
    133 Since `tracforms-0.4` you must grant form-related permissions to the relevant groups and/or users. Otherwise only users with 'TRAC_ADMIN' permision will be able to see details and use forms.
     133Since `tracforms-0.4` you must grant form-related permissions to the relevant groups and/or users. Otherwise only users with `TRAC_ADMIN` permision will be able to see details and use forms.
    134134These are the permission actions available:
    135  FORM_VIEW:: view form details, similar to ticket or wiki change history
    136  FORM_EDIT_VAL:: enable submission of form content changes - these users will be able to see and use 'Update Form' buttons
    137  FORM_RESET:: enable incremental and full form version clean-up by using additional action buttons on form details pages
    138  FORM_ADMIN:: inherits all previous permissions, nothing more yet
     135 `FORM_VIEW`:: view form details, similar to ticket or wiki change history.
     136 `FORM_EDIT_VAL`:: enable submission of form content changes - these users will be able to see and use 'Update Form' buttons.
     137 `FORM_RESET`:: enable incremental and full form version clean-up by using additional action buttons on form details pages.
     138 `FORM_ADMIN`:: inherits all previous permissions, nothing more yet.
    139139
    140140=== About i18n/l10n support