Modify

Opened 5 years ago

Closed 3 years ago

#5318 closed enhancement (fixed)

Unable to specify the width of input or textarea in a TRAC Form

Reported by: anh@… Owned by: rharkins
Priority: normal Component: TracFormsPlugin
Severity: normal Keywords: text input size documentation
Cc: Trac Release: 0.11

Description (last modified by rjollos)

I'm attempting to create a form that would allow us to generically define tasks associated with a ticket and mark them off when completed. TRACForms seems like it would be very useful in this capacity. However, one annoying thing is that I can't seem to specify the width of the input or textarea boxes. Is there a way to do this?

Here is an example form that we would want to include in a ticket. The idea is that we could type in individual tasks for the form and then the engineering team could check off tasks as they are completed.

{{{
#!TracForm
#! submit_label "Finished!"
#! track_fields

|| '''When''' || '''Who''' || '''What''' || '''Task #''' || '''Description''' ||
|| [tf:task1] || [tf.when:task1] || [tf.who:task1] || 1 || [tf.textarea:task1_notes] ||
|| [tf:task2] || [tf.when:task2] || [tf.who:task2] || 2 || [tf.textarea:task2_notes] ||
|| [tf:task3] || [tf.when:task3] || [tf.who:task3] || 3 || [tf.textarea:task3_notes] ||
|| [tf:task4] || [tf.when:task4] || [tf.who:task4] || 4 || [tf.textarea:task4_notes] ||
|| [tf:task5] || [tf.when:task5] || [tf.who:task5] || 5 || [tf.textarea:task5_notes] ||
|| [tf:task6] || [tf.when:task6] || [tf.who:task6] || 6 || [tf.textarea:task6_notes] ||
|| [tf:task7] || [tf.when:task7] || [tf.who:task7] || 7 || [tf.textarea:task7_notes] ||
|| [tf:task8] || [tf.when:task8] || [tf.who:task8] || 8 || [tf.textarea:task8_notes] ||
|| [tf:task9] || [tf.when:task9] || [tf.who:task9] || 9 || [tf.textarea:task9_notes] ||
|| [tf:task10] || [tf.when:task10] || [tf.who:task10] || 10 || [tf.textarea:task10_notes] ||

}}}

Attachments (0)

Change History (7)

comment:2 Changed 4 years ago by rjollos

  • Description modified (diff)

comment:3 Changed 4 years ago by hasienda

  • Keywords text input size added
  • Type changed from defect to enhancement

If it's "only" annoying and not an announced feature, then it's certainly not a defect, right?

Anyway, at least for textarea input fields following syntax works for me:

[tf.textarea:annotations (keine) 40 5]

comment:4 Changed 4 years ago by hasienda

  • Keywords documentation added

Is this solved?

At least for the textarea it really should. Even the quite mature wiki documentation mentions this for ages... Simple one-line input fields are much harder, normally formatted with CSS these days, AFAIK. I'm still unsure how to approach this without a major effort.

comment:4 Changed 3 years ago by hasienda

(In [10151]) TracFormsPlugin: Add optional 'size' argument to input field, refs #5318.

comment:5 Changed 3 years ago by hasienda

(In [10152]) TracFormsPlugin: Add optional default content argument to input field, refs #5318.

comment:6 Changed 3 years ago by hasienda

Current trunk code now recognizes optional arguments for default content and size similar to textarea, what should be as intuitive as possible. Official release is planned for 0.4 and syntax documentation has been updated accordingly.

comment:7 Changed 3 years ago by hasienda

  • Resolution set to fixed
  • Status changed from new to closed

(In [10216]) TracFormsPlugin: Releasing version 0.4, pushing development to 0.5, closes #5318, #5608, #5667.

Codename 'Nelso'. ;-) This is the first release supporting PostgreSQL for
storing forms data, effectively working equally well with all db backends,
that are currently supported by Trac itself.
Another big step towards a stable plugin. Thanks to all the kind people,
who helped with their contributions in many ways. It was another rewarding
experience to find the kinks and iron them out.
Now everybody enjoy the new Trac power under the hood.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.