shanedell commented on issue #1376:
URL:
https://github.com/apache/daffodil-vscode/issues/1376#issuecomment-3220973746
I mean that makes sense but what about more advanced use cases such as:
- Wanting to check that the generated TDML is the same or different between
different runs of the parse.
- Comparing a generated TDML file from one schema to another.
- E.g. Comparing the PCAP schema's generated TDML with the PNG schema's
generated TDML
- Wanting to append a different TDML file's data to the current TDML open.
- Such as opening a TDML file inside of a schema's repository but wanting
to append the TDML of a different TDML file inside of that same repository.
Maybe users won't always want to do these things but I think allowing the
option to do them would be good and prevent any further issues.
I think defaulting to the temp directory is perfectly fine but I still think
there should still be an option of allowing the user to change the path and
name of this file if desired. I get not wanting the file picker to open
everytime especially if the user doesn't want to change the location.
Something we could do is have Create/Append not open a dialog every time
they are ran but instead maybe add a couple components to the TDML Editor that
will enable the user to update the TDML file path used only if they want to.
Meaning, adding components such as a component that displays the path to the
TDML being used and then beside or underneath that a `Browse` button that opens
the file picker dialog when clicked. The default location is
`${OS_TMPDIR}/generatedTDML.tdml` but when `Browse` is selected and a new valid
TDML file was selected the path component value is updated, otherwise it just
stays the default. When Create/Append is then clicked it grabs the value inside
of the path component and never directly prompts the user for the file path.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
