Marketplace versioning with embedded resource

I’ve taken a little “detour” again. I wanted to make it configurable what “rule types”, defined by MIME/media type of the action script, that will skip the “rule page” and go straight to “script page”, for read-only rules. Today, all read-only rules go directly to the “script page”, which I don’t think is ideal.

To do this, the configuration parameter needs to accept multiple text values, and since the MIME/media types can be hard to remember, I thought it would be helpful to define “options” for the most common ones so that they can simply be selected.

However, the MainUI “editor” for multi-value text parameters, especially with options, is hard to use. So, I’ve tried to redesign it to be more useful. Today, what you get it basically a “text area” where you have to enter one value per line (this isn’t described anywhere, so you have to guess it). The “options lookup” only works on the first line, so you can only select one of the options, and have to type the rest.

I really dislike making web UI stuff, so this has been somewhat of a pain for me, and it’s not perfect (I think it should be possible to reorder the values, but that’s just too much for me), but I think it’s at least more usable now. Basically, a new blank “value” will always appear at the bottom, as soon as you type something in it. You can remove individual values by pressing the x, and you have working “options lookup” on every value.

Any views on this? It could become a separate PR, as it has really nothing to do with what I’m doing here, except that I wanted to make such a configuration parameter, and didn’t really think the current solution was sufficiant.