Yes, I think we should provide a standard way for extensions to provide a
settings UI, accessible from the management UI ("settings.html", perhaps).-Nick On Thu, Feb 12, 2009 at 10:27 AM, Alex Russell <[email protected]>wrote: > Sorry to be late on this: > > 2009/2/10 Aaron Boodman <[email protected]>: > > > > On Tue, Feb 10, 2009 at 6:14 PM, Matt Perry <[email protected]> > wrote: > >> Does anyone else have any thoughts about scripts vs full HTML? > > [ snip ] > > > I don't think that we should provide an automatic way to get to this > > page through the UI, though (for example via the management UI). That > > would impose extra work on developers to make this page presentable. > > Instead, we should have an (optional) key in the manifest for > > declaring what URL to use for the "about" or "manage" page. The URL > > can be a web URL, it can be inside the extension, or it could even be > > this master/index page. > > What about *another* (optional) page for config, then? I agree that > overloading the execution context seems the wrong way to handle this, > but as Chrome extensions get ever more sophisticated and begin to > resemble apps, users will want ways to understand what's installed, > control the config, etc. > > Maybe it's something we can defer. Dunno. But it strikes me as > something we'll need SRTL. > > Regards > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
