Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
User interface
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Apr 2011 at 17:03 UTC
Updated:
26 Aug 2011 at 18:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerwhat about "and/or/ rearrange"?
Comment #2
dasjosounds good
Comment #3
jcarlson34 commentedTo keep it consistent with the other drop down option names, should we call it sort instead of rearrange?
How about "sort by and/or"
Comment #4
johnvI'd go for 'sort/and/or'.
Comment #5
Noyz commentedSize matters hare. We use And/Or because the drop button default to the size of the largest label. Unless the buttons are changed to allow for bigger sub-buttons, I don't think you want to change. Here's why...
1. Yes, And/Or is not the perfect label. But you can learn what it does pretty quickly. Said differently @dasjo said it was "somewhat confusing" which also means he learned how to use it.
2. If the buttons on the main query get too large, the entire UI could feel more complex/squished. As such, you'd potentially be jeopardizing the full experience for the And/or task
That said, If the buttons don't expand by default, but expand only to show the sub elements, it's less of a problem. However, I was led to believe that "sort" doesn't really matter? Said differently, if there are no "groups" and one changes the filter sort order, it has no effect. Is that not true?
Comment #6
dawehnerFor example the filter sort order is used for exposed filters.
So if you have multiple exposed filters you can order them as you want.
Comment #7
jcarlson34 commentedWhy not just call it "sort"? Using Noyz's logic above, people will learn about the and/or pretty quickly since it is a option available when sorting filters.
Comment #8
johnvOr change all 'sort' to 'arrange'. This way, every filter/relation/fields section has the same name, and 'arrange' may or may not include sorting/grouping/AndOr-ing.
Comment #9
merlinofchaos commentedPersonally I prefer 'arrange' to 'sort' anyway, but that's because 'sort' has a slightly different meaning for me that's less correct.
Comment #10
dawehner#1131100: Ability to Sort/Arrange Exposed Filters
Another example that the current naming might confuse some people.
Comment #11
michaelfavia commentedNot to bikeshed too much here but i agree with 'arrange/sort' for a few reasons:
1. 'and/or' has almost no inherent meaning to most people and people are much more likely to click on paths that offer incremental and immediate promise to improve their current situation. (while you and i might like to explore our options and see what the tool can do most people just want to get the job done).
2. They can discover the cool grouping functionality which, imo, is a subset of the general sorting and arranging functionality.
3. 'Arrange' more accurately represents what you can do to the filters by creating filter groups, etc.
Comment #12
dasjofrom my point of view: good UI design should make UX intuitive, users shouldn't have to learn just because the UI didn't guide them right
Comment #13
merlinofchaos commentedNoyz: If the filters are exposed, then the filter sort order does matter, since that controls what order the elements will be displayed in. I suspect I'm the one that told you that filter order does not matter, and I had forgotten the exposed bit at that time. It does matter after all.
Comment #14
johnvBTW, in the upper right corner, under 'edit view name/description' is another variant: 'reorder displays', where you can also delete/remove a display.
It is arguable if 'removing/deleting' is part of 'arrange', but an alternative like 'manage' is too broad.
ATM I'd say: default = 'sort'; 'sort' + something = 'arrange'.
Comment #15
Noyz commentedI think "arrange" could work. It's not without issues though. Some thoughts...
1. Arranging only comes into play if you take the step to expose the filter. Exposing filters is not a feature one would do right out of the box
2. Operating requires no additional steps, and might be something one would do out of the box.
3. Summing up points #1 and #2, And/or implies operate and works for the out of the box experience, Arrange does not suppor the out of the box experience, and does not imply operate.
4. The start of this thread mentioned it was weird to click "And/Or" and get "rearrange filters." Such an issue could be fixed by changing the title to something more operand like, e.g., "Operate on filters", or "Apply operands and arrange filters," Apply conditions to filters" I'm not sure if any of these are the solution, just pushing on this a little.
At the end of the day, I tend to think sticking with And/Or and renaming the following page would be a better solution - since it's supportive of the out of the box experience. However, if you were to move to "Arrange," it's potentially a quick learning experience, and would work with the dropbuttons, as well as other buckets (e.g., arrange fields).
Comment #16
jcarlson34 commentedHmm... I hate to add more options here but what if we just called it "edit"
But I'm also cool with arrange or whatever else you all decide on.
Comment #17
merlinofchaos commentedIMO, 'edit' wouldn't lead to the right mental model in any case.
I'm fond of 'arrange', 'and/or' has its own problems. I'm not sure if the dropdown imposes a length limit, so we could go with the longer text which tries to include both.
Jeff: Do you think the word 'logic' would trigger and/or in people? Technically the system is simple boolean logic, though I'm having trouble convincing myself the word is valuable there.
Comment #18
dasjoso "arrange" doesn't convince because it lacks the information of "and/or" and "and/or/arrange" would be too long.
so we would need a more generic word like "manage", "logic" or maybe just "details"
Comment #19
Noyz commented@merlinofchaos, i don't think "logic" would work as well because it requires guess work. I'm still falling on the original (and/or) for the reasons outlined in #15.
Although, part of the problem here sounds like it's related to the drop-button implementation. For example, if the solution started out as "And/Or," and expanded to "And/Or, Sort" (or similar - point being something longer) if when a filter is exposed, I think the issue would be resolved. For example: https://skitch.com/jeff.noyes/rhk37/adobe-fireworks-cs5
This is how I originally intended the drop buttons to work anyways.
Comment #20
dawehnerHere is an image if you use And/Or/Rearrange. It doesn't look too bad for me.
Comment #21
johnvIndeed, it seems like only the name of the first line is critical for overviewing the UI. The other options are like any other drop-down menu. The more explicative the item-name, the less issues are raised :-)
So, #20 seems OK - summing up every functionality in the sub-items might be the best option after all.
Comment #22
dasjoi would go for #20
Comment #23
Noyz commented#20 is hard to read. Usually operators are all capped. AND/OR, rearrange would probably work better.
Comment #24
dawehnerSo here is a patch.
Comment #25
johnvAmazing how a small word can create this many confusion :-)
I am happy with the results of the patch , but keeping #19 in mind and noticing that
$rearrange_text = t('And/Or, Rearrange');results in the menu-text 'and/or,rearrange', I'd either 1) change the texts to small characters or 2) make a remark in the code about capitalization.Comment #26
rhouse commentedYou said: "Arranging only comes into play if you ... expose the filter."
Perhaps I want to arrange them because I know one filter will knock out 99% of the possibilities, so I want to put it first for efficiency? Also "Arrange" can imply context - arranging clothes on a chair is different than arranging them on a person, even if they all occupy the same relative positions.
BTW, I just spent 2 hours trying to find out how to rearrange the filters, so for me (frustrated and grumpy right now), "and/or" is a hopelessly bad choice. I know what and/or does and I didn't want to do it, so I never clicked there. This will be number 1 on the list next time drupal.org commissions a usability study. OTOH, people who want nonstandard operators between their filters have most likely used the module for some time and will already know where to go anyway.
Call it "arrange" and be done with it.
Comment #27
longwave+1 for "arrange"
Comment #28
dawehner@johnv
I think it's currently wanted to be small, because all other items have written with uppercase but displayed as lowercase.
Because many people had problems figuring this out, commited this 7.x-3.x