On Mon, Feb 23, 2009 at 11:29 AM, Matt Perry <[email protected]> wrote: > Interesting thoughts. This is sounding more like Android's "services" > (long-running background tasks) and "activities" (apps run in response > to a user action) model. > > One thought I had in response to this is, who would display the UI? > We'd be able to do something primitive in the browser, like static > button + text, but for more complicated things, we'd want an HTML > renderer.
We'd have to see how far we could get with just simple images and other declarative layout. For example, you could declare an image with different states, and that the states should change depending on whether certain types of elements exist in the rendered page. We'd still need the ability to spin up extension processes to render bigger UI, like when a dialog needs to be opened or a sidebar needs to be displayed. And we might still eventually want the ability to use HTML for more full-featured toolbars. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
