Re: Feature matrix filter - Mailing list pgsql-www

From Thom Brown
Subject Re: Feature matrix filter
Date
Msg-id CAA-aLv41856KuDt3BgBxLoik0cDpAu15VnkHFH_0skxx2JmnKg@mail.gmail.com
Whole thread Raw
In response to Re: Feature matrix filter  (Dave Page <dpage@pgadmin.org>)
Responses Re: Feature matrix filter  (Thom Brown <thom@linux.com>)
Re: Feature matrix filter  (Dave Page <dpage@pgadmin.org>)
List pgsql-www
On 29 May 2013 21:16, Dave Page <dpage@pgadmin.org> wrote:
> Hi
>
> On Wed, May 29, 2013 at 7:01 PM, Thom Brown <thom@linux.com> wrote:
>> Howdy all,
>>
>> Whilst at PGCon I briefly discussed with Stefan the idea of providing
>> a jQuery-powered filtering system for the feature matrix.  This is
>> because it's becoming increasingly bloated.
>>
>> Prototype attached.  This should have no effect on those who have
>> Javascript disabled.
>>
>> Feedback welcome.
>
> A couple of things spring to mind:
>
> - I think it's more natural to have the checkboxes after the labels,
> not before, e.g.
>
> 8.3 [x] 8.4 [x] 9.0 [x]
>
> (I actually found it quite off-putting having them the other way around).

I agree as it happens.

> - By default, perhaps we should only show supported versions and
> betas/alphas, so the grid isn't too big when the user starts.

Easy enough.

> - Should we automatically hide obsolete features if they're obsolete
> in all displayed versions? Maybe that should be a checkable option (on
> by default) shown below the list of versions along with "Hide
> unchanged features"

That should be the case with the "hide unchanged features" checkbox
checked anyway.  The rule is, if it's the same value across all
displayed versions (regardless of whether they're all "Yes", "No" or
"Obsolete"), the row becomes hidden.

Updated version attached.

--
Thom

Attachment

pgsql-www by date:

Previous
From: Dave Page
Date:
Subject: Re: Feature matrix filter
Next
From: Thom Brown
Date:
Subject: Re: Feature matrix filter