Opened 17 years ago
Closed 13 years ago
#3523 closed defect (fixed)
Request for more information and/or examples of context and variables
| Reported by: | C. M. | Owned by: | Steffen Hoffmann |
|---|---|---|---|
| Priority: | normal | Component: | TracFormsPlugin |
| Severity: | normal | Keywords: | documentation |
| Cc: | Trac Release: | 0.11 |
Description
Great Program - opens Trac up for our use. Would you please provide some additional info or examples on context and subcontext as well as how to use subcontext with variables.
I'm having trouble using the debug command - could you also give explicit instructions.
Thank you very much.
Attachments (0)
Change History (11)
comment:1 Changed 15 years ago by
| Keywords: | documentation added |
|---|---|
| Owner: | changed from Rich Harkins to Steffen Hoffmann |
comment:2 Changed 15 years ago by
| Summary: | Request for more information and/or examples of Context and Variables → Request for more information and/or examples of context and variables |
|---|---|
| Type: | enhancement → defect |
In contradiction to wiki:TracFormsPlugin/Syntax I've found, that the criteria argument to the env_debug operation ([tf.env_debug:]) is not optional.
To display all variables you need to specify an appropriate wildcard. I still feel, that displaying everything is a good default for a debug operation, so I'll track this as a bug from now on. Thanks for stirring this issue up.
comment:3 Changed 15 years ago by
(In [10146]) TracFormsPlugin: Make criteria argument to env_debug operation optional, refs #3523.
Now this debug operation complies with the documentation, that always suggested this behavior.
comment:4 Changed 15 years ago by
Replying to ctmurphy:
I'm having trouble using the debug command - could you also give explicit instructions.
See the example in our dedicated section in the tutorial.
comment:5 Changed 14 years ago by
| Keywords: | needinfo added |
|---|---|
| Status: | new → assigned |
Please tell me, are you still looking for more documentation, or is your demand satisfied by the aforementioned wiki doc additions/enhancements?
comment:6 Changed 14 years ago by
Satisfied with the current state?
Would be good. Anyway an explicit statement here would be better. After all it has been you calling out a documentation bug for TracFormsPlugin, and I took quite some hours of my precious time to fix it by means of a greatly extended wiki documentation. Worth some lines of feedback? I sincerely hope so.
comment:7 Changed 14 years ago by
| Keywords: | needinfo removed |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Ok, this went not too well from my point of view.
I really expected you to respond a bit sooner after asking for more documentation. After fixing the code and spending some more hours to improve the wiki documentation as mentioned before, I can't see what to do about it anymore.
Sad to say, that waiting here for feedback seems rather pointless by now, but it's out now for more than nine months. So it's reasonably safe to assume, that this issue has been resolved. I'll close this issue when pushing the code change to next stable release.
comment:8 Changed 14 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Ups, really wanted to keep it open for the release.
comment:9 Changed 14 years ago by
| Status: | reopened → new |
|---|
comment:10 Changed 14 years ago by
| Status: | new → assigned |
|---|
comment:11 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Seems like all objectives of the OP has been fulfilled, finalized by recent additions, that have already been driven by another ticket. Probably a good time to consider this one as resolved.



Still relevant? Or has the wiki documentation been sufficient in the end? After all it's a wiki, and you could even add your findings there...