Great start.  I'm a little confused by the .  Is there a card involved?  Is the value stored in the db?

I'd love to get how this is going to work. Will it let you put a search box where you can type something in and only get results that are cards of a given type (or any arbitrary WQL-defined subset)?

  --John Abbe.....Wed Apr 28 16:18:29 -0700 2010

This seems like a really powerful idea, but I really don't get the proposal very well from the above text.

I'm guessing that this is so we can use the powerful Wagn searching capabilities to make the UX more interactive and allow for a lot more complex contextualized completions and such. This seems like the browser (Javascript) is doing a lot of the work and sending what? A complete query? Couldn't it just send a set of parameters expected by the filter and have all the absolutizing going on in the server much like it does for *navbox and Pointer item searches now? The browser then just presents the options mostly as links.

Or am I just confused by this ticket?