Opened 14 years ago
Closed 9 years ago
#94 closed task (duplicate)
Readable display of parse trees and expressions
| Reported by: | kilian | Owned by: | kilian |
|---|---|---|---|
| Priority: | P2 | Milestone: | v2.3.0 |
| Component: | core | Version: | 2.0.0alpha |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Parse trees (e.g., show (cuts)) and expressions can be printed on screen and in the logfile, but currently only in the full tabular form that is useful for debugging. For informational purpose, a concise and readable representation would be preferable.
Change History (10)
comment:1 Changed 14 years ago by
| Priority: | P3 → P5 |
|---|---|
| Status: | new → assigned |
comment:2 Changed 14 years ago by
| Milestone: | v2.0.0final → v2.0.1 |
|---|
comment:3 Changed 14 years ago by
| Milestone: | v2.0.1 → v2.0.2 |
|---|
comment:4 Changed 14 years ago by
| Milestone: | v2.0.2 → golden-classics |
|---|
That's really a non-issue today, I'll put it somewhere else.
comment:6 follow-up: 7 Changed 10 years ago by
Due to its easy syntax and since it is very suitable for tree representation, I would suggest to use DOT for this task. Whizard could convert the tabular form to a DOT file. Might also be nice for mother daughter relations of particles.
comment:7 Changed 10 years ago by
Replying to bchokoufe:
Due to its easy syntax and since it is very suitable for tree representation, I would suggest to use DOT for this task. Whizard could convert the tabular form to a DOT file. Might also be nice for mother daughter relations of particles.
No, there is already a parse-tree version of the output. What is missing is a condensed version as a mathematical (i.e., Sindarin) expression, a normalized version of the input.
comment:8 Changed 10 years ago by
| Milestone: | golden-classics → v2.3.0 |
|---|---|
| Priority: | P5 → P2 |
This is a concrete part of the plan for #544.
comment:9 Changed 9 years ago by
This is probably also part of #544, I believe. Maybe I can be done in one "Aufwasch".
comment:10 Changed 9 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | assigned → closed |
Definitely part of #544.
Technical internal stuff, therefore moved to technical upgrade 2.0.1.