+chromium-dev bcc: chromium-extensions (this is more of a topic for chromium-dev since it's about modifying the browser and not about writing extensions, which is what chromium-extensions is for)
I replied separately to Xiomei, but for others' benefit, the step that's missing here is adding definitions to chrome/common/extensions/api/extension_api.json. That's the step that actually exposes an API to javascript in extensions. Erik On Thu, Aug 13, 2009 at 9:32 AM, Xiaomei Ji<[email protected]> wrote: > I would like to get some pointers on how to start to prototype new extension > APIs. > Say for example, if I need to add an extension API: > chrome.i18n.getAcceptLanguages(). > I need to: > 1. declare/define "i18n.getAcceptLanguages" as a const char[] in > extension_i18n_module_constants.h/cc > 2. declare/define the API class and RunImpl() method in > extension_i18n_module.h/cc > 3. add the new files into chrome.gyp > 4. register the new extension functions into factory in > extension_function_dispatcher.cc > After build chrome, looks like "chrome.i18n" was not recognized. > There must be something (binding?) I missed, appreciate any inputs. > Thanks, > Xiaomei > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
