[moving to chromium-dev, as it seems better for this discussion] Kelly,
Sorry for not replying earlier. I'm a little bit underwater right now, as we're trying to get everything with extensions tied up so we can turn it on by default on dev. I'd like to take a step back and ponder why even do this as an extension. I assume your end goal must be to build this feature into Chrome's dev tools, right? If so, I think it would be better to start out building the code into Chrome, not on top of the extension system. There is a significant cost to adding APIs to the extension system. They must be general, relatively safe, and we must maintain them, forever. In this case, I don't see a huge demand for these kind of APIs. Even in Firefox, which has infinite flexibility, we only see a few of these type of extensions. In contrast, when something is part of Chrome directly, there is a lot more power and flexibility available. - a On Wed, Aug 5, 2009 at 9:28 AM, Kelly Norton<knor...@google.com> wrote: > If you're interested in what the mechanics of this would look like, an > initial patch for this is posted here: http://codereview.chromium.org/159882 > > /kelly > On Tue, Aug 4, 2009 at 2:39 PM, Kelly Norton <knor...@google.com> wrote: >> >> I've added a document to the chromium wiki that describes an extensions >> API to support a performance tool, which is being called APU for now. For >> those who haven't seen the tool, there is a very brief demo in this >> video: http://www.youtube.com/watch?v=S5aJAaGZIvk#t=21m15s. The API is >> essentially a firehose of timing data that can be enabled on a per-tab >> basis. We're hoping this API is a good starting point for DevTools-related >> APIs in that it has a narrowly focused initial use case and very little API >> surface area. I'm interested in getting your feedback. >> http://code.google.com/p/chromium/wiki/ExtensionsPerfTraceAPI >> Thanks, >> /kelly >> -- >> If you received this communication by mistake, you are entitled to one >> free ice cream cone on me. Simply print out this email including all >> relevant SMTP headers and present them at my desk to claim your creamy >> treat. We'll have a laugh at my emailing incompetence, and play a game of >> ping pong. (offer may not be valid in all States). > > > > -- > If you received this communication by mistake, you are entitled to one free > ice cream cone on me. Simply print out this email including all relevant > SMTP headers and present them at my desk to claim your creamy treat. We'll > have a laugh at my emailing incompetence, and play a game of ping pong. > (offer may not be valid in all States). > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
