Hi Dianne. - Any chance that Google has this kind of modification on the horizon? I think it might be an increasingly popular request given the conflicting requirements for smaller and smaller devices with larger and larger screen real estate.
Another consideration is using android for internet-tablet / net PC kinds of devices, ie.e with lots more screen realestate than say, an iPhone sized device. The limitation of one-fullscreen-activity-at-a- time would really start to grate when you have the space available to do more. Really, the dual-screen thing is a bit of a furphy, what is really needed is more of a windowing/application management system that supports multiple non-fullscreen apps running active concurently. Obviously Android wasnt originally built with that in mind, but if it wants to maintain momentum/mind share, its going to have to look at that limitation sooner rather than later dont you think? Very interested in the thoughts of the Android team on this,. cheers Steve On Feb 15, 8:34 pm, Dianne Hackborn <[email protected]> wrote: > As I replied before, this is going to be very non-trivial to do, and will > require that you at least get a good understanding of WIndowManagerService > and ActivityManagerService. The former is the component that decides how > windows are placed on-screen, and the latter is the one that manages the > stack of activities and tasks. > > The first thing you'll probably notice that the concept of a single stack of > application-kind-of-things is firmly baked into both of those, so allowing > for two such stacks is going to require significant restructuring of those > parts. > > > > On Sat, Feb 14, 2009 at 8:49 PM, saroj <[email protected]> wrote: > > > Hello all, > > > I need to split the Android screen into two parts and run 2 > > applications (app A and app B) simultaneously. app A will run on > > screen 1 and app B will run on screen 2. Both are visible to the > > users. I need to implement this thing in the Android Framework. > > > How to do it ? > > > Waiting for your valuable inputs..... > > > Regards, > > Saroj K Pradhan > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support. All such questions should be posted on public > forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
