[chromium-dev] Re: Working on a new feature? Add extensions support.
I think Aaron's mail makes the point, but just to be clear: before starting coding any new APIs, please send a rough proposal to Aaron and myself. We'll put together an API design based on your proposal and then send it around for broader feedback. Then we'll start looking at the CLs. Our turnaround time is pretty fast on this, so don't expect this to be a heavyweight process. thanks, Erik On Mon, Jul 13, 2009 at 5:17 PM, Erik Kay wrote: > If you're not working on any new features or new UI, you can probably skip > the rest of this email. > > If you are, then please take the time to think about whether your feature > should be accessible from extensions. Hopefully, "no" should be more of the > exception than the rule. > > It turns out that adding extensions support is pretty easy. Here's a > recent sample CL that adds a getLanguage() function that uses compact > language detection: > http://codereview.chromium.org/150062 > (it's a fair number of files, but the changes are small and easy to > understand) > > Feel free to send questions to the list. We're happy to help with > everything from basic how-to questions, to API design, etc. > > Erik > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Working on a new feature? Add extensions support.
We (the core extensions subteam) typically spec all new APIs and send them out for comment to the wider team. This helps keep things consistent and is easier since we are most familiar with the capabilities of the system. - a On Mon, Jul 13, 2009 at 10:25 PM, Darin Fisher wrote: > What is the review process for new extension APIs? > -Darin > > > On Mon, Jul 13, 2009 at 5:17 PM, Erik Kay wrote: >> >> If you're not working on any new features or new UI, you can probably skip >> the rest of this email. >> If you are, then please take the time to think about whether your feature >> should be accessible from extensions. Hopefully, "no" should be more of the >> exception than the rule. >> It turns out that adding extensions support is pretty easy. Here's a >> recent sample CL that adds a getLanguage() function that uses compact >> language detection: >> http://codereview.chromium.org/150062 >> (it's a fair number of files, but the changes are small and easy to >> understand) >> Feel free to send questions to the list. We're happy to help with >> everything from basic how-to questions, to API design, etc. >> Erik >> >> > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Working on a new feature? Add extensions support.
What is the review process for new extension APIs? -Darin On Mon, Jul 13, 2009 at 5:17 PM, Erik Kay wrote: > If you're not working on any new features or new UI, you can probably skip > the rest of this email. > > If you are, then please take the time to think about whether your feature > should be accessible from extensions. Hopefully, "no" should be more of the > exception than the rule. > > It turns out that adding extensions support is pretty easy. Here's a > recent sample CL that adds a getLanguage() function that uses compact > language detection: > http://codereview.chromium.org/150062 > (it's a fair number of files, but the changes are small and easy to > understand) > > Feel free to send questions to the list. We're happy to help with > everything from basic how-to questions, to API design, etc. > > Erik > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
