Open Stack

Currently there is no hook for customizing the javascript filtering behavior. A patch for that would be more than welcome.

My warning, though, is that this is a can of worms I've been loath to touch. Until we (and by we I mean OpenStack) have a really complete, robust, consistent story across all the APIs for bth filtering and pagination there is no good solution to this problem. It involves one-off hacks for each service and even for different routes within a service's API. It's quite gross.

The short-term option (which we've favored by relying on the Javascript filtering almost exclusively) is to pull in as much data from the APIs as possible and do any and all filtering on the client side. This solution isn't fully built out either but it's a better stopgap measure if you want to help build it out.

All the best,


-          Gabriel

From: Oliveira, Volmar (Brazil R&D-ECL) [mailto:volmar.junior at hp.com]
Sent: Wednesday, February 06, 2013 9:20 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [horizon] Filter - client x server

Folks, I reported an issue regarding distinct behavior between client side filtering and the server side.
https://bugs.launchpad.net/horizon/+bug/1117459

an example, in the user dashboard we have server side filter using only name and email columns, and the horizon/static/horizon/js/horizon.tables.js
Implements using all available columns.

I have to implement the filter for Images dashboard, someone know some workaround for this? Where/How can I implement a client side filter to match server side one?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130210/2615c8ea/attachment.html>