Am 22.01.2010 um 02:15 schrieb Brian Wang: > [snip] >> >> And to say more, just like I did with Guarana's list, we should >> abstract the model it uses, providing functions to check the number of >> items and get items given its index. That way we can write those >> functions that query SQL and no need to actually create a list with >> 1000 elements in order to show it. > > I'm not an expert of this, so bear with me. :-) > You mean saving items into an SQL database and SELECT them on demand? > If the database is on a disk (not RAM), wouldn't it be slow when the > list is scrolled around due to the querying? If the database is in > RAM, how is it different from the current implementation in terms of > memory footprint?
It's very different, as you can apply several interesting tricks like paging and caching (i.e. only loading what will actually shown, grabbing 20 or 30 per SQL request etc.) and -- if you have the proper infrastructure -- cancelling requests for items that have already been scrolled out of the visible area. :M: ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
