On Sep 26, 4:23 am, James Dempster <[EMAIL PROTECTED]> wrote:
> I'm releasing a preview, to get some feedback on the UI.
>
> One of the things I'm struggling with is where and how I should go
> about adding support for table level filtering, the column level
> filtering seems fine. Should I simply add another filter icon just
> above the table?
Good work so far. I'll definitely be using this in the future.
After using it though, I am unenthusiastic about the usability.
1. The popup box is distracting and requires me to think too much. I'd
prefer to see a text field instead of the funnel icon and when focus
is put on the field, the extra options are displayed (maybe through
slideDown) directly below it. There would only be one option though, a
checkbox, that says "Match case" (to follow IE's and Firefox's lingo).
See #2.
2. The plugin should know what I want instead of requiring me to tell
it.
a. I think it should always assume "case insensitive" unless I check
the box that says "Match case".
b. If I enter ONLY a number, it should assume numeric (which, if I
enter only one number, is the same as matching as text anyway). And it
should definitely assume numeric if I enter a range modifier like > or
< or -.
c. Regular expressions are an advanced topic that a normal user would
never utilize so I think it's reasonable to force the user to enclose
the regex in forward slashes. /[a-z]{2}/
d. If someone wanted to search for the string /[a-z]{2}/ and not
actually do a regex they should enclose it in double quotes. "/[a-z]
{2}/"
3. For the table wide filter just put the same filter widget (textbox)
with a label saying something like "Table wide: |____________|" or
"Filter whole table: |___________|" or "Find in table |___________|"
or "Filter all: |____________|".
4. Also it'd be good for numeric filtering to have a range operator.
e.g. 10-40 "ten through forty"
5. And lastly, it'd be great to apply multiple filters just by
separating them with a space. This would be useful in tables that have
a whole name with more than two names and where the user doesn't know
the whole name. "John William Smith Jr." I should be able to type
'john jr.' to find him. If I wanted to find an exact match of 'john
jr.' then I would enclose it with double quotes '"john jr."'
That's my 10 cents. :)
Chris.
