Is it difficult to change the widget to a DropdownWidget instead of the ButtonGroupWidget? If it's alright, then it should also be the same layout where Optional is already selected and they could just change to another in the dropdown. I guess also if it's ok, then this should be a new ticket?
Live on the test instance.
This was an existing problem, but the priority buttons are wrapping awkwardly regardless of zoom level:
@WMDE-Fisch I'm realizing that waiting on feedback for just the VisualEditor repo doesn't make sense. Let's go ahead and expand the experiment to include the other repos we're heavily branching, starting with CodeMirror and TemplateData, if you agree? I'll mirror those two, and I've added instructions to this task about how to mirror additional repos, under "Mirror a new repo from Gerrit".
Tue, Sep 22
I tried reproducing this on enwiki, by changing the TemplateData "description" multiple times. I was unable to cause corruption.
"no description" text should be above deprecated warning. Wrong:
Fix placeholders and non-image media files.
Looks like the infobox is missing one of its nested templates? Would you mind also pulling in "italic title"?
vagrant@mediawiki-vagrant:/vagrant$ mwscript importDump.php --wiki=enwiki /vagrant/xml_imports/en-T263521.xml
Mon, Sep 21
Are the inline help strings listed somewhere? I can glean most of them from the mockup, but some are truncated...
@thiemowmde Does this really need review or can it be demoed now?
Fri, Sep 18
@ECohen_WMDE There's already an OOUI standard layout for inline help text:
Note to self: "Same size applies to the parameter editing screen" -> this will happen by default, the parameter editing screen is implemented as a pane in the template editor dialog.
Moving to review so that we can start collecting data.
Note to self, both the VE 2017 wikitext editor and the 2010 source code editor share the usecodemirror preference.
The "review" request is for other devs to go through all the steps and post their observations on this task.
Thu, Sep 17
Rebased and resolved some minor merge conflicts. This is live on the test instance.
Wed, Sep 16
Yes, if possible the three dots is much preferred. Thanks!
Tue, Sep 15
It looks like the local "query imageinfo" API is able to return thumbnail URLs for commonswiki, I'll try to integrate with that.
Mon, Sep 14
Confirmed the same behavior in the original patch. It depends on the filename, I got lucky with a long name including many short words: "User overlap bug.png". Results from the server are nondeterministic, and I've seen nothing show up in the first hundred matches. Even more alarmingly, setting the limit to 200 caused server memory exhaustion, reporting that it had tried to allocate 700MB before crashing.
We're keeping this task open to iron out any last issues, the merge with other features was non-trivial and may have broken things.
Porting the branches to gitlab was really a pleasure. The basic process was,
Thu, Sep 10
@ECohen_WMDE This is only about the VisualEditor? Or should the TemplateWizard be modified as well?
We need to act on this, we're 11 patches into a branch on the VisualEditor repo alone, and it's becoming difficult to replicate the test instance locally for further development.
The TemplateData part of this feature is live on the test instance.
Fixing might be as simple as adding allowLanguages to the property descriptor.
Should the "Deprecated guidance" header end with "(en)" like the other text inputs, and be translatable? I think this is correct because the message will be used in the interface. For now, I'll leave the string untranslateable for consistency with the shortcoming documented in T262526: TemplateData deprecated parameter guidance should be translatable.
Wed, Sep 9
We can capture the preference toggling by adding the preference name to an inclusion list in WikimediaEvents PrefUpdateInstrumentation::PROPERTY_TRACKLIST.
Ready for demoing again. An earlier patch had inadvertently removed the example and parameter deprecation notices from the description text.
Mon, Sep 7
Remove the 'Add more information' dropdown at the bottom of the main input area, where parameters are currently added to templates.
There needs to still be a way to add unknown template parameters. For example, when the TemplateData is incomplete and has not been updated to document a newly-implemented parameter.
I suggest we either leave "add more information", or have a button that does this.
When a template has hundreds of parameters, I worry that this might fall apart:
The sidebar will display all parameters, not just those that have been added. The parameter icon to the left of the parameter names is removed and replaced with "+"/"-" buttons (same buttons & behaviour as in the TemplateWizard sidebar). These are used to add and remove them to the template, i.e. shown in or removed from the main input section on the right.
Is there an affordance to search template names?
Reducing the estimate, there wasn't much left to this ticket.
Fri, Sep 4
Wow, do *not* do what I did. Force push was a total disaster:
Minor thing: the dialog title is currently the template name (see below), but should we change that to "Insert a template"?
It didn't work so well. The branch isn't forwarded when using the repo over anonymous HTTPS.
So far, I've done this with the VisualEditor repo. We have a branch wmde-templates and QWERTY staff are allowed to push or force-push.