year an a half after....
* is still impossible to protect code of extensions? is not any option to sign the crx file or something like that. Is it possible to protect small at least small parts of the code containing the sensitive stuff?
* supposing that a payed service is created, this would mean that there is not way to prevent any user editing the code and bypassing the payment verification source code. Is that correct? Whic is the approach to integrate a payment mechanism in an extension?
* I need to package several extensions so I would like to do it programmatically. However, I had some issues working with
chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pe
is there any small java jar or classes (from Chromium core) which allows packaging an extension programmatically? (I guess that chrome.exe should invoke some Java code in Chromium)
Share your ideas please. Thank.