You can't replace the recent apps UI in 1.0, though that would be a good thing to support in the future. You can write your own task manager that the user gets to through another mechanism, though.
Thanks! On Sep 24, 7:54 am, Razor1973 <[EMAIL PROTECTED]> wrote: > Dianne, > > Thank you for your explanation. > > I actually do like this for the most part. However, there are cases > in which I do want to know which applications are running and which > are not. For example, what if I am running an instant messenger and > decide to log off and keep working on something else and hours later, > I open the list of recent applications? The messenger will be there, > yet, unless I remember, I won't know whether I am still signed on or > not unless I click on it and re-open it (or bring it back from the > running background processes; irrelevant from what you say). Am I > correct? Again, for the most part, I like the way Android implements > this, but there are cases in which an old school task manager would be > more useful. > > Now, is Android so open that it is technically possible for someone to > build an actual task manager that fully replaces the recent > applications functionality and allows the user to see only the running > apps and kill them if he/she wants? > > Thank you again and congratulations on the amazing job you guys have > done with Android. This is only the first version. I can only > imagine what the platform will be like a year from now! > > Ray G. > > On Sep 23, 10:40 pm, hackbod <[EMAIL PROTECTED]> wrote: > > > That is not a list of running applications, it is most recently used > > applications. Some of them may actually be running, some may not, but > > it's not something you need to be aware of. > > > In a very course way, yes, the design is like Windows Mobile where the > > system takes care of killing apps as memory is needed. However, the > > way this is done is very very different, and is designed from the > > ground up to not be something that users need to deal with (which also > > means that it is a fundamental of how all applications interact with > > the system, which helps us make it work well). Our goal is that from > > the user's perspective, all applications are running all of the time, > > and the fact that their processes are being killed and returning as > > the system runs is not something the user needs to care about or is > > ever aware of. > > > Just let the system run and do its thing and all will be happy. :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
