Ticket #109 (closed enhancement: fixed)

Opened 2 years ago

Last modified 10 months ago

One should be able to set the minimum for fetched table row count

Reported by: Henri Muurimaa Owned by: Matti Tahvonen
Priority: minor Milestone:
Component: Server-side framework Version: 4.0.0-beta1
Keywords: table row fetch Cc: marc.englund@…
Known Issue description:
Hours estimate: 2 Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: no Contract:

Description

Currently table fetches only the rows that are displayed. This results in speed-wise unneccessary loads when scrolling a short table.

Change History

Changed 2 years ago by Jani Laakso

  • owner changed from Marc Englund to Matti Tahvonen
  • hours_left set to 2
  • version set to 4.0.0-beta1
  • affects_documentation unset
  • milestone set to 4.0.1

This should be added to Table API if not exists already, Matti please check this.

Changed 23 months ago by Matti Tahvonen

  • cc marc.englund@… added
  • status changed from new to assigned

I'd like some comments from real users of Table component (read : Henkka and Marc).

This can currently be done by also using setHeight from Sizeable interface like this:

table.setPagelength = 600;
table.setHeight = 300px;

BUT IMO this is bit ugly way to do this, because this forces Java-developer to know how client side works. Assume that table has n+2000 rows. What now exactly happens, is on first load user gets 600 rows and then client JS automatically fetches 3 * 600 rows for cache purposes, so there will be 2400 rows loaded and rendered totally (which is pretty heavy.

What I'd consider better would be to make "cacheRate" a configurable option on Java side. Then Java developer could set "height" by only defining how many rows to show for user and still adjust caching. I'd look something like this:

table.setPagelenght = 10;
table.setCacheRate = 7.7;

"Now there would be ten rows shown to user (at once), but 77 rows would be fetched in background to smoothen scrolling."

Changed 15 months ago by Jani Laakso

  • milestone deleted

Milestone 4.0 Candidates for next release deleted

Changed 10 months ago by Jani Laakso

  • status changed from assigned to closed
  • resolution set to fixed
  • affects_release_notes unset

Cleaning ticket database, closing obsolete bugs and enhancements.

Note: See TracTickets for help on using tickets.