Added ability to change placeholder text for comment/tag, and make comment replies optional #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to be able to disable the replies in the comment widget without actually disabling comments for a smoother experience were annotation tasks will not involve collaboration.
Specifically I'd like to make
Annotorious
initialization to optionally be invoked as follows (modified from this example):Again, you get similar behavior with the
readOnly
flag, but then a user cannot modify the comment at all. Alternatively a user could simply use the tag widget with an unfixed vocabulary for this purpose, but there are still some use cases where that's not ideal. What's more you can't actually add a custom placeholder to indicate a different kind of annotation task - that could also be a reasonable PR to make if it was desiredFor example, you may want to annotate some OCR by both identifying the part of speech (from a fixed vocabulary described in the tag widget), as well as correct any misinterpretations of the read text (via the 'comment' widget).
The final thing added in this PR is the ability to change placeholder text for either the comment or tag widget. Making the final instantiation look like:
All these new fields are totally optional, and should change any existing behavior of the tool. Finally, my apologies for the additional whitespace changes - my text editor automatically removes trailing whitespace which seems like a decent enough practice - I hope it's not too distracting.