PreValue config - swap dropdown with a "Doc Type Picker"

[leekelleher]

Rather than using a dropdown, we could do similar to how the DocType "Allow children" permission UI works. Use the overlay directive to display a doctype picker.

https://github.com/umco/umbraco-inner-content/blob/develop/src/Our.Umbraco.InnerContent/Web/UI/App_Plugins/InnerContent/views/innercontent.doctypepicker.html#L20

This is purely a cosmetic / consistent UI idea.

[leekelleher]

I'm thinking along the lines of the List View's layout control...

Where the "icon" picker would be a document-type, the "Name" and "Layout path" would be for the Name Template and Tab dropdown respectively.

[dnwhte]

Considering tackling this along with #43 since both involve changes to the doctypepicker. You mention "Tab dropdown". Inner Content currently doesn't have a Tab dropdown and supports tabs in the edit view. Are there plans to change this?

[leekelleher]

Ignore the Tab drop-down, we removed the feature in v2.0, 15a7d44

[dnwhte]

Quick prototype.

[leekelleher]

The prototype looks great, thanks! 🎉

Couple of technical points...

1. Let me know if the JSON value/schema changes for the prevalue data. There are things we can do to manipulate it, in order to keep backwards-compatibility. (I've got code examples where we've done this previously). If there are no changes, then no worries. 🙂
2. With the PR for this, you mention about Feature: Doc Type groups #43 too. If you could do them as separate PRs, that'd be great, otherwise it becomes trickier to review.

[dnwhte]

No changes to prevalue data needed. I will submit as a separate PR.

One question, do you feel it is safe to use the existing list classes in core or should I copy the styles and create new classes?

[leekelleher]

I'm happy to use the existing list classes.

[leekelleher]

Closing this ticket as a PR has been submitted. Further discussion can be had on PR #45 - thanks @dnwhte! 🎉