Boolean Chart Redesign

[Justin Wood (Callek)]

On 7/18/2010 4:03 AM, Max Kanat-Alexander wrote:
> On 07/17/2010 07:52 PM, David Marshall wrote:
>> I think they're pretty easy to understand, actually.  Each Boolean chart is
>> AND'ed with everything else.  A Boolean chart, which can be individually
>> negated, has rows that are AND'ed together.  Within each row, there are
>> columns that are OR'ed together.
>
> 	You are also one of the few people intimately familiar with the code of
> Search.pm.
>

I think I am too; since I actually read Search.pm to try and figure out 
how to do a certain query. [of course I gave up on my end-result with it 
though]

>> It is certainly not easy to do with with a Boolean chart, but it's possible!
>> However, I don't want to explain DeMorgan's Law to anyone who would then
>> need to apply them to a Boolean chart.
>
> 	There *are* logical groupings that are impossible, though, with the
> boolean charts, because you can only NOT individual whole charts, so
> DeMorgan's Law cannot be applied.
>

Which also makes some searches LONGER... I mean, I had tried to create a 
complex search which found existing bugs IN a product/component combo; 
that was in a Product and NOT in {set of known components}.

My solution is probably 20x slower than need be, since it gathers a 
fairly large list of bugs, and trims them down; rather than gathering a 
fairly small list, and adds to them.

>> I omitted the rest of Max's mail, but I want to chime in that I hate the
>> notion of a parentheses button.  We have a number of management-type users
>> at Yahoo! who just don't grok operator precedence and the need for
>> parentheses.
>
> 	Okay. Do these manager types currently use and understand boolean
> charts? Parentheses are not *necessary*, they are just used to add
> operator precedence. If you fail to use them, the chart UI will work
> similarly to how it does now.
>
> 	The proposal isn't about a UI for manager types or non-engineers--in
> fact, it's not even about UI at all. Right now, I'm designing a backend
> system that can be used to build queries. Once we have this, there are
> already plans in place (known by at least pyrzak and I) to design a
> simple search system that could be used by non-engineers very
> effectively, but this email thread has absolutely nothing to do with that.

My only request on the UI-Side is that the boolean chart can be 
expanded-out with JS rather than GET/POST requests to add a row/column/etc.

p.s. I'd also LOVE if backend could support POST for at least the 
boolean chart to help avoid this "query-string-too-long" bug. [the UI 
could possibly even try and catch this issue, and POST instead of GET 
just in case] ;-)

-- 
~Justin Wood (Callek)
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla