People grid needs sortable columns

[JimPGlenn]

Department is clickable but doesn't lead to sorting.

refer to https://github.com/pauleveritt/pyramid_bottlecap/issues/86 for history.

[Chris Rossi (chris-archimedeanco)]

I think we need a quick huddle on this one. The UX1 grid uses the client side karlgrid, which seems to use the jquery ui grid. So the UX2 grid needs to use this too, if we're going to keep the sorting. But the javascript is generating html in code with its own classes, etc. so it might be hard to reconcile.

[Paul Everitt (paul-agendaless)]

If you'd like, we can devote Balazs to owning all flavors of grids. He'll probably SlickGrid-ify everything.

--Paul

On Mar 29, 2012, at 3:11 PM, Chris Rossi wrote:

> I think we need a quick huddle on this one. The UX1 grid uses the
> client side karlgrid, which seems to use the jquery ui grid. So the UX2
> grid needs to use this too, if we're going to keep the sorting. But the
> javascript is generating html in code with its own classes, etc. so it
> might be hard to reconcile.
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/956008
>
> Title:
> People grid needs sortable columns
>
> Status in KARL3:
> New
>
> Bug description:
> Department is clickable but doesn't lead to sorting.
>
> refer to https://github.com/pauleveritt/pyramid_bottlecap/issues/86
> for history.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/956008/+subscriptions

[Chris Rossi (chris-archimedeanco)]

I'm happy to pitch in on the work for this, but I'd at least like to consult with Balasz and maybe Blaise, as they've been owning js and css respectively so far. I haven't seen Balasz on irc today so maybe he is out. Given that, it looks like this one might slip to next week.

[Paul Everitt (paul-agendaless)]

I'm going to hand this to Balazs for next week. I believe he is committed to SlickGrid-ing everything.

[Paul Everitt (paul-agendaless)]

I'm going to be aggressive and say "nobody uses this" and close this. We can re-open if it actually gets used. But isn't a good use of budget at this point to implement this.