Skip to content
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

[Improvement] widget HTML export uses native ag-grid code only #11

Open
vincent-grosbois opened this issue Dec 4, 2022 · 1 comment

Comments

@vincent-grosbois
Copy link
Contributor

This issue is to track a potential improvement on this lib.

Currently, the HTML export of ipyaggrid Grid component is based on the "automatic" export of ipywidget components to HTML ( cf https://ipywidgets.readthedocs.io/en/7.6.3/embedding.html ) . This is fine (in case it works), but possibly the generated HTML/js code is bloated/slow, because it has to embed ipywidget JS dependencies etc. In essence, when we do ipyaggrid HTML export we now have gone full circle, because we have a html/js lib (ag-grid), wrapped in python, wrapped in js, again exported in HTML :D

A possible way to improve this would be to add another HTML export method, where ipyaggrid would manually generate the "pure" ag-grid code, with only dependencies on ag-grid and not on ipywidgets

@mariobuikhuizen
Copy link
Contributor

Thank you for your patience; I apologize for the extended period it has taken for us to address this issue. To help us evaluate the viability and impact of your proposed change, could you please provide some metrics? Specifically:

  1. The difference in size that would result from your proposed change
  2. The impact on load time
  3. An estimate of the code changes required, both in terms of lines of code and complexity

This will help us make an informed decision. Given our limited resources, we'll need to weigh the performance gains against the maintenance and implementation costs. If the benefits are marginal and the effort required is significant, we may have to respectfully decline this proposal. Thank you for your understanding and contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants