-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filtering on click #141
Comments
Doesn't look too intuitive (IMO), at least not when the filter is located above the column (maybe if it was in far away form/location it would make more sense). Can't think about something right now, will comment again later on |
I guess that a new property can be added, something like 'externally_triggered' that will remove the filter action from the filters and you will use the exFilterColumn later on. |
Absolutely. Much more intuitive when using an external form. To go a bit further, what do you think of a |
exFilterColumn can already handle filtering multiple columns at once, see docs https://github.com/vedmack/yadcf/blob/master/lab/jquery.dataTables.yadcf.js#L186 |
Indeed! Thanks! Looking forward the |
Hi Daniel, Any update on this one? Or any idea when do you plan to work on it? |
Hopefully in the following days, after current version will go final. so just to be sure I got you, you are planning to place bunch of filters into some form and let the user to play with them and them user has to click so button "filter now" and only then the table will get filtered based on the values in the filters? |
Great!
Absolutely. Note:
Hope it helps! |
Just saying that there wont be individual reset buttons for filters when you will use the externally_triggered mode and... externally_triggered will be applied to all filters, you wont be able to mix filters that will work as normal and some that will be triggered externally , what do you think? |
Makes a lot of sense to me.
<3 |
Working on it, till now added to select / multi_select / text / auto_complete , you can see it on http://yadcf-showcase.appspot.com/dom_source_externally_triggered.html |
Looks great Daniel!
Any idea? Note that the
|
working on externally triggered #141 questions can be now asked on stackoverflow with 'yadcf' tag
that issue should be solved in 0.8.8.beta.4 |
It's working great with the v0.8.8.beta.4. Now I'm encountering another issue with an AJAX source which contains a null object. Actually the exact same issue as #113. Let me try to provide an example... |
I haven't tuned this feature for ajax yet, so I think you better delay your tests on ajax |
Alright! (but still trying to provide an example :-)) |
Should work now for all filter types with dom/ajax/server... let me know how it goes for you... only thing left is to make a better looking showcase page - will pull the filters out of the table into some form... |
Thanks Daniel. I'll test it as soon as I can and get back to you. |
Actually I forgot that I planned to move the |
…nitMultipleColumns externally_triggered can be set for yadcf constructor /init (and not per column) , see showcase http://yadcf-showcase.appspot.com/dom_source_externally_triggered.html #132 #141
externally_triggered can be set for yadcf constructor /init (and not per column) , see showcase http://yadcf-showcase.appspot.com/dom_source_externally_triggered.html |
You mean now it can be set using both the constructor and column definitions? |
Yep |
Updated the showcase externally triggered page a bit |
Hi Daniel,
Do you have any idea about how I could change the default behaviour of filtering on keyup and replace it by a click?
The goal is to delegate the action of filtering to an extra button, as shown is the following example:
Regards,
Thibault
The text was updated successfully, but these errors were encountered: