A quick-and-dirty throwaway proof-of-concept that you use to measure the actual impact of the proposed change is actually a very decent engineering method in this case. E.g. hardcode a cache on the SD card and see if it's faster to load from that cache than from internal storage.
Cheers, JBQ On Thu, Jan 15, 2009 at 5:28 PM, Freepine <[email protected]> wrote: > Yes, a patch would always be better to prove your idea:) We should always be > prepared to take the risk of preparing some code to prove our ideas:) > That's pretty a programmer way:) Just kidding~ > > On Thu, Jan 15, 2009 at 11:18 PM, Mike Hearn <[email protected]> > wrote: >> >> > I know that the author of Home has been under lots of pressure to make >> > it start as quickly as he possibly could, because startup time has >> > consistently been a visible issue. >> >> Why does it have to read every app installed to render the apps on the >> home screen? It's scanning for the launch intents, right - can't it >> persist the desktop icons into a cache and rebuild that cache when the >> "app installed/uninstalled" intent fires? For bonus points that cache >> could be on the sdcard. >> >> (i know i know ... i should write a patch .....) >> > > > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
