Ticket #1983 (closed enhancement: fixed)

Opened 3 months ago

Last modified 2 months ago

Table should update its column widths according to the data in container

Reported by: -Sami- Owned by: Marc Englund
Priority: minor Milestone: User Interface Library 5.3.0 RC
Component: gwt-adapter-client Version: 5.2.5
Keywords: Cc:
Known Issue description:
Hours estimate: 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 (last modified by Joonas Lehtinen) (diff)

I'd like that Table would update it's columns widths accordingly when data in container changes.

See http://forum.itmill.com/posts/list/477.page for discussion.

Happens also with latest nightly build. (15.8.2008)


This is an design issue and needs planning, changing type to enhancement

Attachments

Ticket1983.java (2.3 kB) - added by -Sami- 3 months ago.
Test case for the ticket

Change History

Changed 3 months ago by -Sami-

Test case for the ticket

Changed 3 months ago by Joonas Lehtinen

  • priority changed from undefined to minor
  • type changed from defect to enhancement
  • component changed from undefined to gwt-adapter-client
  • description modified (diff)
  • milestone set to User Interface Library 5.3.0 RC

Changed 3 months ago by Matti Tahvonen

  • owner changed from Marko Gronroos to Marc Englund
  • status changed from new to assigned

Assigning this to Marc per forum discussion.

Supporting this in our current Table will be very complicated. Would for sure need a separate rendering mode that would always try to adapt to width and this would rule out many of current features.

IMO wontfix for this. We would need a separate lighter table implementation (no scrolling, reordering, column resizing etc) to both client and server. This "feature" would sit fine there.

Changed 2 months ago by Marc Englund

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

Implemented in [5389]

However

This is sort of a questionable feature - the use case is valid and there is no easy way to add this functionality when-needed, but Table is specifically made to maintain column widths to avoid skipping when lazy-loading (there is no way to know how wide future content will be).

The current implementation is marked experimental and can only be enabled by extending Table and setting alwaysRecalculateColumnWidths = true.

We need to carefully think about this to avoid making the already complicated Table even more complicated. Is there a better way? Is this feature indeed incompatible with lazy-loading, and should be moved to a non-lazy table implementation?

Closing and creating 'review' ticket #2066

Note: See TracTickets for help on using tickets.