We are using jplist (with Require.js) for our filtering and sorting purposes and it works fine. We have a wrapper kind of a module which defines jplist.core and other bundles as dependencies.We then use this wrapper's init method to initialize jplist, build the UI for sorting, filtering and pagination.
Now we have few screens which are not data heavy and hence client side filtering suffices and few others where having a server side implementation makes more sense. Since server side details are handled in core-ajax, we are having issues when we try to use both core.js and core-ajax and this breaks the page.
Is there a way to disable the dataSource option and enable it where we need it?
Hi,
We are using jplist (with Require.js) for our filtering and sorting purposes and it works fine. We have a wrapper kind of a module which defines jplist.core and other bundles as dependencies.We then use this wrapper's init method to initialize jplist, build the UI for sorting, filtering and pagination.
Now we have few screens which are not data heavy and hence client side filtering suffices and few others where having a server side implementation makes more sense. Since server side details are handled in core-ajax, we are having issues when we try to use both core.js and core-ajax and this breaks the page.
Is there a way to disable the dataSource option and enable it where we need it?