Andrei, That's a good response. I think you convinced me to not do it.
Instead, I wonder if it is possible to do something like what other web apps do (Twitter and even the new GWT google group), which is to keep adding rows as one scrolls down. I've experimented with range change event handler. Maybe that would be a more modern way to provide tabular data? Mike On Wednesday, May 9, 2012 7:13:33 AM UTC-7, Andrei wrote: > > If your data never wraps within a cell, then the height of the row is > always the same - it is determined by the CSS. (As a sidenote, you can > change it in your CSS, or even apply different heights to different > tables). > > Else, > > 1. The height changes as data wraps within a cell. Thus, you can't > know the actual height of the row until the table is rendered. > > 2. If the height changes with data (some rows have longer data and > wrap, other rows don't), what's the point of changing the number of > rows? Your first 10 rows may take 240 pixels, the next 10 rows can > take 330 pixels, and so on. > > Also, remember that data can wrap more often when columns are > narrower. This means that if you want to predict the height of your 10 > rows, you also need to take into consideration the width of each > column. > > 3. Users can change the size of the font in their browsers, unless you > disable it, which is not a good practice. They can also resize their > windows, add or hide toolbars in their browsers, etc. You just can't > avoid having a scroll-bar. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/sEq0Vi47ztQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
