There is a *major* usability issue in Panels interface. I'm not using Panels very often, so it's always the "first time" I use it and it's extremely confusing. It took me 20 minutes to find the mini panels preview tab. Heck, this is very good made hidden!
In "admin/structure/mini-panels/list/[my custom panel]/edit/content" I thought the »
lead to a breadcumb and not to something that can be clicked to see details of a configuration.
The style of these wizard trail links should be changed to tabs secondary or buttons style.
Comment | File | Size | Author |
---|---|---|---|
#15 | ctools-1496514-15.patch | 1.43 KB | basvredeling |
Comments
Comment #1
hass CreditAttribution: hass commentedLooks code wise that ctools is the source of this code.
Comment #2
hass CreditAttribution: hass commentedAlready better than today, but unstyled.
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedThe problem is that this change is really only relevant is "free trail" is set to true. Sometimes it truly IS a trail and the items are not clickable, and sometimes it is more of a menu and the items are clickable.
Comment #4
merlinofchaos CreditAttribution: merlinofchaos commentedThere's some work in a branch of CTools to create a Page Manager style UI as a general CTools Export UI pattern. That might ultimately be a better fix since it changes stuff like this to vertical tabs. That may, ultimately, be the right way to handle these things.
Comment #5
hass CreditAttribution: hass commentedYeah, vertical tabs sounds like a really good solution. Any reference case?
Comment #6
merlinofchaos CreditAttribution: merlinofchaos commentedThere's no issue, but I believe the branch is operations-ui (in CTools) -- the actual work is for the pipeline UX in Panels (pipelines branch in Panels). Ideally we would've had that completed prior to Drupalcon but sdboyer got busy with non-Panels stuff and didn't get to the point where we could merge that into the mainstream.
It's some pretty complicated work.
Comment #7
DamienMcKennaAlso for consideration: #1775234: Local tasks on MiniPanels edit pages are confusing
Comment #7.0
DamienMcKennaa
Comment #8
DamienMcKennaIn the interest of resurrecting this, how about just changing the DOM structure ever so slightly so that it appears as pseudo local tasks, ala #1775234: Local tasks on MiniPanels edit pages are confusing?
Comment #9
basvredelingProblem
This issue arrised for me when handling the new Openlayers 3 interface (see #879130: Alter the use of "Clone" for exportable objects in code).
I also read the thread in #1775234: Local tasks on MiniPanels edit pages are confusing
But I don't like the approach for the fix there.
2 remarks:
In #1775234 they've chosen to overwrite the divider and align the list to the right.
But what really should be done is:
Just take a look at some UI patterns concerning wizards: http://ui-patterns.com/patterns/Wizard or https://www.pinterest.com/ruth77rn/ui-patterns-wizards/
The Drupal 8 Seven theme proposal overhaul for secondary tabs is also interesting: https://groups.drupal.org/node/283223#Navigation_Tabs
Proposal
For real wizards we adopt an ordered list like so:
Next we remove the option for a "free trail" and output these situations as stated in #2
Furthermore, the wizard should probably include a "active" theme variable to style the finished wizard elements and the current / future elements independently. For style I propose building on the study done in https://groups.drupal.org/node/283223
Comment #10
basvredelingHere's a simple patch. Should be reviewed for both free trails and linear trails.
If you must use the divider as it was, the " » " can be reintroduced with css by adding:
Comment #11
basvredelingOh, and it needs a review.
Comment #13
basvredelingComment #14
Chris Matthews CreditAttribution: Chris Matthews as a volunteer commentedThe 4 year old patch in #13 to wizard.css and wizard.theme.inc does not apply to the latest ctools 7.x-1.x-dev and if still applicable needs a re-roll.
Comment #15
basvredelingHere's a new patch... not 100% sure how relevant this still is though. Old remarks about styling and hardcoded >> still apply.