Closed (fixed)
Project:
Diff
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
4 Oct 2016 at 07:08 UTC
Updated:
26 Oct 2016 at 13:34 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #2
tduong commentedComment #3
tduong commentedAdded description to the diff plugins and displayed them on the settings page. I guess that the description after the "Layout" table (marked in red in the screenshot) now could be removed since then it is kinda repeating the description provided for each of these rows.
Anyway, any improvements about the descriptions ?
Comment #6
johnchqueI like this approach but I think it might be better to fallback in something when the description is not defined.
And if we gonna add this, it's better to add it in diff/src/Annotation/DiffLayoutBuilder. :)
I don't think is needed to add the plugin name in the description.
Instead of "This plugin is configurable" IMHO could be better to write "Field plugin settings are applied to this layout."
Comment #7
miro_dietikerAlmost all list builder of config entities / plugins i know of look like this:
admin/structure/types
So a separate column with the description.
Comment #8
tduong commentedAdded a "Description" column. I don't get how we will use the property created in diff/src/Annotation/DiffLayoutBuilder. About the descriptions, I've used a similar template like in \Drupal\sharemessage\Form\ShareMessageForm::form() unsing the Drupal\sharemessage\Plugin\sharemessage\Addthis/OGHeaders/Sharrre plugins, where the plugin name appears again in the description. Do you still want to remove it ?
Comment #10
johnchqueSince Visual layout cannot be installed in testbot, this line should go away.
Comment #11
tduong commentedRemoved that line, not sure how to make the test to run/detect the implementation from a hook_help().
And I'm still wondering if we still need to keep that description below the table.
Comment #13
miro_dietiker@tduong See help.module's HelpBlock.php
"This page provides the configurations about the" => "Configurations for the"
The plugins don't offer a configuration form on their own. But indeed the second has a setting (what theme to use) so i would skip the "This plugin is [not] configurable".
I thought both split fields and unified are as much like GitHub.
Comment #14
tduong commentedAdded
help_blockin the test, edited the descriptions.Not sure if it is fine as it is right now, how would you warn the user which layout plugins he/she can configure per field at admin/config/content/diff/fields otherwise ?
Comment #15
johnchque"Configuration" might fit better.
We want to avoid the diff word in the UI, better to change this to: "The layout plugins that are enabled to display the revision comparison."
This area layout plugins, So change it to This configurable layout plugin... or "This layout plugin uses...
Comment #16
tduong commented1. I think "Configurations" is fine, since there are more than one. Miro's comment at #13 suggest it as well.
2-3. done
Comment #17
johnchqueOK, then.
Comment #18
miro_dietikerIMHO the help at admin/config/content/diff/fields is not yet satisfying. It should mention that it affects the two (unified, split) field plugins
Comment #19
miro_dietikerI also just realised that the "Leading/Trailing context lines" only apply for the split/unified fields.
Should we apply some Fieldset around plugin specific settings?
- Field based plugin settings.
- Visual Inline plugin settings.
The plugins description could refer to being "field based". Or we instead mention both in the fieldset.
Comment #20
johnchqueChanged a bit the comments, Also added changed the settings screen to be like:
Not sure if the wording is good enough.
Comment #21
tduong commentedYeah, these "per category settings details-wrappings" could be easier for the end user/self-explaining, but then for the visual_inline_theme aren't the label "VISUAL INLINE LAYOUT SETTINGS" and the description "Theme used for Visual inline layout when comparing revisions." too much/repetitive ?
Not sure, but imo, if we would keep it like this, I'd suggest removing the description (or at least saying something more "useful", like the Leading/Trailing examples ?)
About "Leading context lines", "Trailing context lines" and their descriptions, not sure which better wording we can use to not repeat things. Maybe just "Leading" and "Trailing" as select labels and keep the descriptions (?)
More:
As you said once "We want to avoid the diff word in the UI" (comment #15.2), how can we change this "For every field, a diff plugin can be selected and configured." ?
Also imo this new help text is too long, but if it is fine, then: "This" --> "These".
Unnecessary new line.
If you change/add new line/block like these kind of lines, you can directly edit the array syntax to avoid later cleanup issues and the possible "resulting conflicts".
Not sure what you mean by "made as the content is rendered for the user".
Comment #23
miro_dietikerCommitted on cross post. Happy to receive another update here.
Comment #24
tduong commentedCreated followup to discuss about the wording stuff: #2817159: Provide better description wording for the Diff settings UI
Set back to "Fixed".