You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I want to build a jupyter widget for displaying Ibis tables. Ibis wraps around SQL, so the tables can be much larger than memory, so I don't want to materialize the entire table and hand it off to ipydatagrid. This means that the sorting and filtering controls need to happen EXTERNALLY to ipydatagrid. I think it would work well if I composed an ipydatagrid widget inside an ipyibis widget: the outerwidget would have controls for sorting/filtering/pagination, making the ibis query and materializing the pandas dataframe, and then it would hand off this dataframe to ipydatagrid for actual rendering. The problem here is that if ipydatagrid exposes its own sorting/filtering UI, then this is confusing to the user, since they would only be operating on a subset of the possibly-much-larger table. I want the only controls to be in the ipyibis widget.
Describe the solution you'd like
A way of turning off the sorting and filtering in the UI. OR, being able to listen to the events, so that I can handle them on the ipyibis side.
Describe alternatives you've considered
Monkeypatching the css or html AFTER ipydatagrid does its thing? IDK how feasible this is.
don't render the header row at all from within ipydatagrid, render it externally. This would be hard to get it to align though.
forking ipydatagrid. Really don't want to do this.
The text was updated successfully, but these errors were encountered:
Any progress on this? I also have a use-case where the filtering/sorting functionality is adding more noise to the workflow and I would like to be able to switch it off.
Is your feature request related to a problem? Please describe.
I want to build a jupyter widget for displaying Ibis tables. Ibis wraps around SQL, so the tables can be much larger than memory, so I don't want to materialize the entire table and hand it off to ipydatagrid. This means that the sorting and filtering controls need to happen EXTERNALLY to ipydatagrid. I think it would work well if I composed an ipydatagrid widget inside an ipyibis widget: the outerwidget would have controls for sorting/filtering/pagination, making the ibis query and materializing the pandas dataframe, and then it would hand off this dataframe to ipydatagrid for actual rendering. The problem here is that if ipydatagrid exposes its own sorting/filtering UI, then this is confusing to the user, since they would only be operating on a subset of the possibly-much-larger table. I want the only controls to be in the ipyibis widget.
Describe the solution you'd like
A way of turning off the sorting and filtering in the UI. OR, being able to listen to the events, so that I can handle them on the ipyibis side.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: