Boolean Chart Redesign

[Max Kanat-Alexander]

On 07/19/2010 02:33 PM, Gervase Markham wrote:
> Would it not make sense to a) look at those and b) talk to some of the
> usability people we have and see if we can come up with a design for
> building queries which is less complicated?

	Well, no matter what UI gets put on the frontend, I'm pretty sure the
proposed backend will be able to handle it. But if you (or an
experienced UI designer) think there are UIs that would benefit from a
totally different backend, then I'd be open to hearing about it.

	I do already know of a UI design for building queries that would be
less complicated--it wouldn't have all the functionality of the boolean
charts, but it would be usable on the Simple Search page. (It would be
something like the Thunderbird filters interface or the Rhythmbox
"automatic playlist" editing interface.) If there are also proposals for
UIs that *would* be able to represent any query (because ultimately,
there are many developers and project managers who are going to need
that), then sure, I'd be interested in hearing about them.

	I'm pretty sure that there are no queries (that can be expressed in
SQL) that cannot be represented by my proposed backend design. So, any
frontend could go on it--but what I'm talking about is the backend, and
then a very simple modification to the existing UI to start with, before
we go and heavily redesign the UI (which is not something we should do
at the same time as heavily refactoring the backend).

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.