-
Notifications
You must be signed in to change notification settings - Fork 2
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
Thank you #3
Comments
Thanks for your interest in this repo! The top priority of dev is to fix bugs and ensure compatibility with latest versions of Jupyter and pandas. I'll also develop new features as time permits, and contributions from the community are highly welcome. The vision for future dev is to keep it small, efficient, and user-friendly, without adding complex functionalities. Feature-wise, I believe the core value of qgridnext lies in facilitating quick EDA (exploratory data analysis) for large datasets. While qgridnext currently offers fast loading times for large data, it lacks convenience in data statistics and visualization. Enhancing these aspects will be a focus for new feature development. Kagglers and data scientists would probably like to view some statistics while filtering data. In terms of maintenance, qgridnext relies on a custom and outdated version of SlickGrid, which complicates bug fixing and compliance with modern web standards. Furthermore, for build system it uses a traditional setup.py, rather than Jupyter Packaging or Hatch, which are more common for modern Jupyter extensions. While a complete refactor is beyond my current capacity, I’m open to merging contributions that can modernize our codebase. This would greatly benefit future development. |
Also Thank you from my side! |
Thank you for the work on this. I know many folks using qgrid and this helps to keep it in play as Jupyterlab is updated.
What your plans for this repo? Continue maintaining? Adopting new features? Having other participate in dev? I am curious on where you see this project going.
Thank you!
The text was updated successfully, but these errors were encountered: