There are a few issues with the user interface that I've noticed while starting to work on this module. I'm guessing this will become a meta-issue and we can break it up into sub-issues.

  • The drop-down that sets whether queries are equal to, not equal to etc needs reworking so that it's clearer: any reason we can't use "=", ">", "<" etc?
  • At the moment, that dropdown looks like it only refers to the top item in the list. This needs reworking. Might need some jQuery goodness.

There will doubtless be other things. UI stuff often needs an over-arching vision rather than being picked apart bit by bit, but I think it's still useful to list the issues.

CommentFileSizeAuthor
#6 Clipboard.jpg100.94 KBJohn Tolhurst

Comments

mitchh’s picture

I use a customized version of this module and I changed the drop down to:
Equal to, Not equal to, Less than, ... Contains string, Does not contain string, Begins with, Ends with
There are no convenient symbols for many of these and occasional users understand the text much better.

Also, I disabled filtering on permissions as this is really a sys admin type feature. In my case the module is used by people managing a member base who would not understand it. I would like to see the option to to disable this in config.

I agree the layout is confusing. The filter button is also at the top. Perhaps this and the operator drop down should sit half way down and not horizontally aligned with any of the options. Still not ideal.

John Tolhurst’s picture

Suppose I have a customer named Travis something-or-other. How do I find him? Oh! The wee box that is part of the first line applies to all the rows. I have used this module for 6 months and never realised that.

I think on reloading the page it should drop previous filter results.

After you [undo] the filter section collapses (d'oh).

Could we not use wildcards? Username = Travis*

BE GT what's that mean?? ... we don't need a new language for simple concepts. Just use existing language, no harm in spelling it out. And now I see the key printed in the hover box. Sorry, I don't want to learn the codes, even though I see they are quite neatly designed.

You are making an ew table for each filter class - you don't need to, just a line break between rows is enough and will keep the thing compact so you probably can keep the section uncollapsed while being used.

It would be great if you could [reset] without waiting for the server to re-load the page - its not like you are wanting any new information (my assumption of course)

When you go to the advanced tab, the filter section needs to be open by default - important, otherwise you get confused that you are in the wrong place - it needs to appear the way it looks when you use it. These might seem trivial I suppose but they are basic ergonomics. I hope something can be added up from the comments.

Anonymous’s picture

The undo function could use a checkbox to know which filters to remove. I don't know how useful the collapsed frameset is either. It may be hiding information that isn't obvious to the user.

Reworking the radio buttons to a select list would help IMO. Then use jquery or #AHAH to fill the values entry to the appropriate type and options. And an appropriate CSS file for the form would be really beneficial to the look. The screen real estate is the reason the operations selection is mnemonicfied. At least the mouse over description gives you the translation. If we change the radio buttons to a list then we can use three rows to get the data instead of columns and then expand the operations text.

Anonymous’s picture

If we use #AHAH I suggest we depend on http://drupal.org/project/ahah_helper to help remove the need for many menu callbacks.

mitchh’s picture

Reworking radio buttons as select and rotating the layout as you suggest gets my vote. Dont know why I didnt think of it :-)

John Tolhurst’s picture

StatusFileSize
new100.94 KB

Please see the attached.

User steps:
call Advanced User
paste or write value (operator automatically changes from 'select' to 'equal')
choose another operator if required
click [filter]
OR select multiple filters at once
OR having seen the selection by scrolling down, add additional filters onto the same screen, or change current filter settings.

This would make it plain from the outset and would reduce all those annoying clicks.

[undo] and [reset], great. print them slightly over from filter, so you can click filter each time without having to actually read which button is the [filter] button.

Advantages:
Less clicks to do anything.
Can edit the full set of filter parameters without waiting for [undo].
Compact enough presentation to have the section expanded all the time (having it collapse when you're in the middle of using it is a real PITA) In fact, please just don't ever collapse it, its the whole reason the user is using the module in the first place.

See the find customer function in ubercart's create order, it uses wildcards

And lets reorder them, starting with the person, the individual and working towards the more abstract functions, the more personal attributes (name) will be more frequently used by those who we need most to smooth the ergonomic path for:
Username
Email
User Id Number (that's the drupal node number?)
Role
Permission
Status
Created
Accessed

John

John Tolhurst’s picture

And I guess each line of the layout I suggested would need to be prefaced with an and/or switch (default =and)
And at the end of each line, [add] to add another line the same joined with an 'or'
And a save query function.

That would be something pretty handy, for carving users lists into marketing segments, assigning the result of the saved query to a role, linking to outside bulk email programs like Mailchimp to send out the membership of a role. (Including a link in that email for members to update their profile, honing their areas of interest, creating better targeted communications.)

Anonymous’s picture

Version: 6.x-2.x-dev » 6.x-3.x-dev
Status: Active » Fixed

I've implemented changes to the user interface and the patch file can be found at #765776: 6.x-3.x changes. The patch includes more than just the interface changes and the reason for the new issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.