Re: Feature matrix filter - Mailing list pgsql-www

On Thu, May 30, 2013 at 6:39 AM, Thom Brown <thom@linux.com> wrote:
> On 30 May 2013 11:33, Dave Page <dpage@pgadmin.org> wrote:
>> On Wed, May 29, 2013 at 10:09 PM, Thom Brown <thom@linux.com> wrote:
>>> 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.
>>
>> Definitely an improvement.
>>
>>>> - 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.
>>
>> Yeah, I get that. I'm just suggesting that obsolete features should be
>> treated differently, as they're even less interesting than something
>> that was implemented before the first version show.
>>
>> Regardless of that, I do think that checkbox should be on it's own line.
>
> Unfortunately the latest version of my distro of choice was released
> yesterday, so after 3 versions of not upgrading I decided to upgrade
> (fresh install), but now I'm on Django 1.4.5/Python 2.7, and I can't
> get the site running locally again. :/

I've got a branch that works with 1.4 (well, ish - markdown is broken,
but in general it works) to be used when we get to wheezy. I can try
to push it up to github tonight or tomorrow so you can work off that
to test things.

--Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/