Separate translation and suggestion status filters

It is an excellent patch

Excellent! +1!

Erm, why not make this more usable? If you look at the screen shot, you see two things set by the dropdown:

- has a translation (T+) or not (T-) or does not matter (Tn/a)
- has any suggestions (S+) or not (S-) or does not matter (Sn/a)

So we have two dimensions, each with three possible values.

All = Tn/a, Sn/a
Untranslated = T-, Sn/a
Has suggestion = Tn/a, S+
Translated = T+, Sn/a

Why add another arbitrary combination, when next time we come up with a need for another one? Why not separate the options then and make a usable selection for translation status and suggestion status independently. Let's come up with a good user interface for this, and if nobody else takes on the coding (although it would be great if you would :), I can do that.

I think, that Sutharsan have offered very convenient variant

I'll have a look at the interface.
Gábor is right that this might be solved in a better way.

Actually three state checkboxes would fit here best. If we would have them. We have yes / no and don't care options, for which the three state checkboxes were born in the first place.

Also suggested at http://drupal.org/node/196865 with a different approach before, which is not really applicable if we need these many dimensions to look up strings with.

Gábor, aren't you pointing to this issue ? #196865 = here :-)

Well, I intended to point to http://drupal.org/node/185281

Here's some patch. Creates a double drop down field like

Status [All/Translated/Untranslated][--/Has suggestion/No suggestion]

About the patch, it's quite small, splits the status filter in two form fields and uses some bitwise magic to keep the status as an integer, so links should work the same.

Wow, way to go, thanks for taking this on! Some notes:

- previous links to status 3 will not work or will be broken with this patch, right?
- there are some smaller code style issues with the elseifs
- I am not sure the status values as in the dropdown are too expressive; seeing "All" "---" does not tell me much. Maybe it would be better to have longer titles (see below).

I was again looking around the net for a tri-state checkbox implementation for jquery (at http://plugins.jquery.com/project/Plugins/category/20 for example, and also all around the net), but could not find one. It does not sound extremely hard to do, so I might take a look at implementing that sometime. With tri-state checkboxes (no, yes, don't care), these two options are easy to capture without the use of dropdowns. Anyway, since it would be a JS implementation, the dropdown will be kept anyway, so I'd like us to refine this patch a bit and commit soon :)

OK, rerolling. Changed the stuff to radioboxes, polished a little bit.

What do you think now?

This is an alternative patch for this and #220107: Allow search for user

It adds a new interface:

But it lacks a PHP implementation. If somebody would like to take care of it, please do so...

OK, had a plenty of time in plane so I implemented a server-side stuff, polished a little bit.

Attaching a screenshot. Please note "Do not save this filter" checkbox, I will probably create another issue for this.

I would be great to make the separated filters each a three state switch (AKA three state checkbox). I have been searching for such a ready-made plugin (yeah, it is surely done on the internet for countless times already). Just recently stumbled on this one: http://www.memorycraft.jp/project/jquery/j3ssw/index.html#tab2 not sure about the quality but helps you get the idea. Check the latest example, which has "yes", "no" and "don't care" items.

Of course that three stat selector would not be a requirement at all, but would be a follow up.

subscribe

so this is called over-engineering
just reroll the patch in #10 because it is the perfect solution, and use the string "<Any>" when nothing is selected, because that is the string what views module use

reasons:
you can search for better string like "Any", "All", "Not selected", "Unspecified", "Choose", "---", "Don't care" or empty string, but none of them are good enough, so just keep the string change to another issue (or followup patch), because that will not be fixed any time soon..

I don't see any benefit with the filter on user who made the translation. Create a new issue for it, if you still think you need that.

use a simple filter, which means use dropdownlistbox or editbox controls. do not use radiobuttons that just take up too much space on the UI, and do not use 3 state checkbox, because it is not used in Drupal and it is a way much more complicated than a dropdown.

Here is a reroll of #10 which actually changes status values a bit more. Decided that those, who ran the server and had bookmarks will just update their bookmarks. Committed this to the module and rolled out to localize.drupal.org.