Changes between Version 14 and Version 15 of WorkFlow

Timestamp:

Jan 30, 2006, 7:13:02 AM (18 years ago)

Author:

Alec Thomas

Comment:

Clarify editable semantics

WorkFlow

@@ -8 +8 @@
  * Add a `disabled` attribute to fields so that workflow hooks can disable fields but still leave them visible.
  * Add a `hidden` attribute for the same reason. I've actually already done this, simply by renaming the `skip` attribute to `hidden`. Did this to be more consistent with HTML.
- * Add a `fullrow` attribute which signifies that the form element will span both columns of the ticket property fieldset. eg. summary, type, description and reporter would all be `fullrow=1` (done, but code in the templates is not implemented). [2833]
+ * Add a `fullrow` attribute which signifies that the form element will span both columns of the ticket property fieldset. eg. summary, type, description and reporter would all be `fullrow=1`. [2833]
  * Remove code specific to individual fields from ticket.cs/newticket.cs. The summary, type, description and reporter would be converted to use the the same generic code as the rest of the fields. [2833]
  * Remove large `if/elif` statement from ticket.cs/newticket.cs. Currently there is a large if/then/else style block which is used to display all fields other than the four described above. This could be removed and replaced with a call to form_control(). [2833]
@@ -16 +16 @@
 
 === TODO ===
- * Add a `.onchange` option for javascript field validation.
+ * Add an `.onchange` option for javascript field validation.
  * Add a `.title` option, or maybe `.tooltip`, though I think for the sake of consisteny it should be `.title`.
  * Add a `checkboxes` field type. This differs from the `checkbox` type in that it is a set of related checkboxes. It would store the data in the field value as `check1|check2|check4`. I'm not sure about this one, or how it would be presented in the query module, but I figured that people might find it useful. Similarly, a `multi_select` type could be useful.
  * Remove `ticket_custom_props()` macro? It does not appear to be referenced.
  * There are a number of locations in the ticket code where permissions are hard coded. As an example, the `TICKET_CREATE` permission is required to create a new ticket. Should this be overridable by `ITicketWorkflow` implementors?
+ * 
 
 == Basic Configurable Workflow ==
@@ -99 +100 @@
  * '''hidden''': Field is not displayed. Useful for storing extra ticket attributes programmatically (false by default).
  * '''fullrow''': Field spans a full row when displayed in the ticket properties.
- * '''editable''': Field is editable (true by default). If a field is hidden but editable, it will not display in the ticket summary but will be displayed and editable in the ticket properties.
+ * '''editable''': Field is editable (true by default if field is not hidden). If a field is hidden but editable, it will not display in the ticket summary but will be displayed and editable in the ticket properties.
 
 Types and type-specific options: