Saturday, November 28, 2015

Re: Optimizing subjective performance accessing big celllists (kind of double buffering)

OK Jens, thx a lot for your answer.

I just render last 10-50 based on the device "capabilities" (kind a tricky, but an iPhone 4 just shows 15 and an iPhone 6, for instance, shows 50) and then have a "load older" button too... But, even with 50, the final end user impression can be optimized.

OK for mapping both places to the same activity then. Will rearrange code and create helper classes for code maintainability... yes, of course we'll give it a try! ;)

Thx a lot.

On Friday, November 27, 2015 at 2:08:19 PM UTC+1, Jens wrote:
I would say: Don't render all available messages at once. Just render the latest 30 message and if the user wants to see older ones the user has to tap a "load older" button or you just load them when scroll panel reaches the near top.

There is rarely a need to render everything up-front especially for messaging apps where conversations are rarely deleted by users and can become pretty long.

If you absolutely don't want that then you probably need to adjust your current mechanism of switching between group/contact list view and the messages view. You haven't said how you switch views, but I guess introducing a third actor that manage both group/contact and message view/presenters can solve your problem. For example if you use GWT Activity + Places you would map both ConversationsOverviewPlace and MessagesPlace to the same Activity. That Activity then manages your ConversationsOverviewActivity and MessagesActivity internally so you can do your own transition logic.

-- J.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment