Some people likes textarea, but in my opinion textarea at admin/build/crumbs still should be converted to tabledrag anyway.

Issues:
- user-friendly (not every PC user knows how to use Copy-Paste functionality; mobile users?)
- easy for mistakes (even there is some kind of validation)
- line could be removed when retyped wrong or removed space
- when typed '-' at the beginning of the text, all rules are removed
- i.e. user have 100 rules, by mistake copying and pasting first inherit rule with the header, removes all rules (no backup?!)
- difficult to understand, which section you can order, and which not (See: #918190: Order confusion)
- scrolling required
etc.

Comments

kenorb’s picture

kenorb commented

Related: #924088: Pluggable plugins

donquixote’s picture

donquixote commented

subscribe.
I'll definitely do something about this sooner or later, but it doesn't have top priority. For now it could be enough to improve documentation.

donquixote’s picture

donquixote commented

Update:
The 2.x branch does still have this nasty textarea.
I played with a js solution on a local install, but I am not quite happy yet. I think this will take some more time.

donquixote’s picture

donquixote commented

Some thoughts.

The current textarea implementation is inspired by "blockadminlight". Except that the crumbs textarea does not have any funky js parsing. For blockadminlight I did get some nice feedback, but I also imagine there are people who don't like it.

Tabledrag is the correct solution for the "enabled" section, where order does matter.
For other sections, I would prefer it things are sorted by module and plugin / alphabetically, not by the user. Think of the blocks configuration interface, where you often have a hard time finding specific blocks in the "disabled" section.

For the "inherit" section it would be useful to show which status these rules currently have, inherited from the parent.

Rules in the inherit section should have a button, checkbox or radio to explicitly enable or disable a rule that is currently set to "inherit" or "disabled by default". This button has to play team with the "enabled" and "disabled" sections.

I did play with color code, but it is getting too colorful.

Instead of "inherit", we could have one big area that shows all available rules and their status.

Possible statuses:
- explicitly enabled
- explicitly disabled
- enabled by default (applies only to '*')
- disabled by default
- inherit, enabled (because the parent is enabled)
- inherit, disabled (because the parent is disabled)

donquixote’s picture

donquixote commented
Status: Active » Closed (duplicate)

Closing this as duplicate of #1404018: Better UI for hierarchical prioritization form.