2013-02-10, 00:13
Let me clarify my original use of "persistent" - when RCB is spending a minute or two loading the games ("please wait, loading games", or some such), it seemed like RCB was adding list items to the gui, one by one, instead of following an mvc pattern, where the game list would be stored somewhere persistent, like an sqlite table, and the list view would only query the database (model) for enough items that fit in the screen. If the user moves down from the list, the list view would fetch more elements from the model, etc. This way that "loading games" delay would disappear, and the gui would be as snappy with 10 or with 1000000000 games.
Hmm, wait, what exactly would get hardcoded in that xml? The list items, or presentation bits as well? If the former, if loading big (several thousands) list from xml is snappy, then it sounds like it'd be good enough. We could have RCB cache the game list to an xml, and only refresh it after rescrapping, or on explicit user request.
Hmm, wait, what exactly would get hardcoded in that xml? The list items, or presentation bits as well? If the former, if loading big (several thousands) list from xml is snappy, then it sounds like it'd be good enough. We could have RCB cache the game list to an xml, and only refresh it after rescrapping, or on explicit user request.