You can make changes to the extension when you're not the author, however, only authors can make the .crx files.
This is a discussion on Packaging - New Method within the Plugins Development section, part of the Chrome Plugins category: At least they implemented a way to package with Chrome. Unfortunately, now it sounds like we cannot make changes to ...
At least they implemented a way to package with Chrome. Unfortunately, now it sounds like we cannot make changes to the extension unless we are the one who created it. Unless I read that wrong.
http://dev.chromium.org/developers/d...ions/packaging
You can make changes to the extension when you're not the author, however, only authors can make the .crx files.
Sorry, that's what I meant. I frequently repackage extensions to help people out.
Awww man.. gotta repackage everything now..
EDIT: We could use a simple UI where you just select the extension folder and the extension key..
I don't feel like typing![]()
devilslackey: Hopefully, this new way to package extensions is easier, and so there's less need to help people. We hope to add even easier UI for creating CRX files in the future, so developers don't even need to really be aware of signing.
Welcome to this Forum, Aaron, and thank you for informing us![]()
Thanks Aaron for lettings us knowCan't wait to see what you guys are going to do next
I could have used a warning on your blog before this release though![]()