On Mon, 2008-09-08 at 17:29 +0800, mike lewis wrote: > Aren't we talking about another scenario though? The menu itself is > static but the scenario of having say a USB based hard-disk full of > media that plugged in after load? I know I'm skipping here but even > if there was an image cache you woudn't want that kind of content > pre-loaded would you?
No, I wouldn't think it sane to preload anything except UI elements. At least not preload in the same sense that I referred to earlier. What I would expect to do is read-ahead 1 or 2 images when you begin viewing images in a directory. > as long as it doesn't block my ability to control the UI navigation > I'm in a hurry.. dischi and I are of one mind when it comes to responsiveness of the UI: most kinds of UI blocking are unacceptable. The API we have in kaa lends itself very heavily to asynchronous design. So for 2.x you shouldn't worry too much about UI blocking. At least not the obvious blocking that can be avoided. Certain things are unavoidable. If we need to load 20 images to display a menu and you've opened that menu, the time it takes to process those images and render the menu is necessarily going to block the UI. It's a design goal to make such things < 100ms. I think in most cases we're well under that. (But dischi knows the GUI side of things better than I do right now.) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
