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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate how much of the vaadin-grid scroller and data-provider can be reused [1 馃晵 * 1 馃懆] #701

Closed
yuriy-fix opened this issue Aug 16, 2018 · 2 comments
Assignees
Labels
needs research More information needed to estimate

Comments

@yuriy-fix
Copy link
Contributor

Child of #657

@yuriy-fix yuriy-fix added needs research More information needed to estimate sprint backlog labels Aug 16, 2018
@yuriy-fix yuriy-fix changed the title Investigate how much of the vaadin-grid scroller and data-provider can be reused Investigate how much of the vaadin-grid scroller and data-provider can be reused [1 馃晵 * 1 馃懆] Aug 16, 2018
@tomivirkki
Copy link
Member

Most likely makes sense first to..

  • extract the <iron-list> fork out from <vaadin-grid> to a separate repo
  • with current <vaadin-grid-scroller> extension (bringing "lazy loading" and "million dollar scrolling" features on top of it) and publishing it as an internal component (name TBD)

..and then..

  • update <vaadin-grid> to use that (small effort)
  • modify <vaadin-combo-box> to use the new scroller element and build the required (clearable) cache layer for lazy loading. Change items API to build on top of the new layer.

@tomivirkki
Copy link
Member

Early proto at https://github.com/vaadin/vaadin-combo-box/tree/data-provider-proto

Note: this proto still uses <iron-list> internally. We can postpone the scroller change mentioned above for later. The feature is included as an additional mixin with very little internal changes needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs research More information needed to estimate
Projects
None yet
Development

No branches or pull requests

2 participants