How would this be done if installing a theme doesn't require any authentication? If we are going this approach, it means the user should be logged in to manage his/her own themes? I like this approach as well... but why not just do this: Create a chrome://themes/ page where we asynchronously fetch the theme data from the remote website, that way, we can control how that page is rendered with prefs (currently installed theme, last 5 installed themes, etc ) we could even make that chrome://themes/ page fetch themes from different sources (not only from Google) via syndication. Just a thought.
Later on, we could even have the chrome://themes/ page create custom colours for themes (once again, easily done by altering the prefs) if the user wants. Add tints, etc ... Many, many people on the forums want custom colours. (Similar to GMail) -- Mohamed Mansour On Mon, Aug 10, 2009 at 1:13 PM, Amanda Walker <[email protected]> wrote: > On Mon, Aug 10, 2009 at 1:05 PM, Peter Kasting <[email protected]>wrote: > >> Or, instead of building this list in locally, we could build it in to the >> themes gallery. When you go there these MRU themes (and the default) are >> right on the first page. This can also help when you're trying to set up >> another machine with the theme you like and need to remember what it is. >> > > +1. This also helps frame the UX as "pick", not "install". > > --Amanda > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
