NightWind's Card Searcher

(09-08-2008 11:55 AM)moonfish Wrote:  What you're explaining is xor, yet you're calling it or.

If it's xor, and you check d, l and g and none of the others, you'd get all monocolor cards. If it's or, you'd get all cards that are dark, light or grey or any valid combination.

And I'm back. Well at least what's left of me anyways.

Reading through all the posts, I think I might have an understanding of what you'd like moonfish. But just in case I make a wrong assumption, can you please provide me with perhaps a few examples of what you want to see and what you don't want to see.

Looking ahead, I might either need to redesign the form to fit the group of checkboxes in - perhaps by reducing the size of the card text box and rearranging some headers to go on the side.

But the problem is how to not do it in such a way so that users don't get confused by all the similar options. I'll have to see if this would run into "Total mana cost between" functionality. Should I disable some fields if a user decides to do a specific search? *becomes confused*

I also need to think about the SQL implications and how it will affect the SQL I already have. Let's hope I can implement this without having to rewrite too much.

---

Oh and I think I'll keep the "include store searcher results" unchecked - the reasons for this outweigh the number of votes to have it checked. Those who have voted for it to be checked do seem okay to leave it unchecked if needs be. And an extra click for some is better than having unessecary scrolling and increased load time for the others.