*Hello brave early extension developers, I have good news and I have bad
news.

Good news:   We're planning on enabling the extensions system by default on
the dev channel soon. Perhaps by as early as this week, the
--enable-extensions flag will no longer be required in dev.

Bad news:
In preparation for this milestone we went through and made some overdue
breaking changes. Some of these were security related and had to be made in
order to go live on dev. Others were just API cleanup that we wanted to get
done while we still could.

The next dev channel release -- hopefully this week -- will contain the
following changes (among others).

=================================================

Permissions


   - You now need to declare the hosts you want XHR access to in the
   manifest.
   - You also need to declare if you want to use the bookmarks, tabs, or
   windows API.


Example:

{
  "name": "My cool extension that needs access to bookmarks and
www.google.com",
  "version": "1.0",
  "permissions": [
    "bookmarks",
    "http://www.google.com/";
  ]
}

More 
information<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/manifest.html#permissions>

 =================================================

API changes

We went through and did some sprucing to improve consistency of the
programmatic APIs.

Renamed module:


   - chrome.self ->
chrome.extension<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/extension.html>
(chrome.self
   still works, but is discouraged)


Changed function parameters:


   - chrome.extension.connect(name) ->
chrome.extension.connect<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/extension.html#method-connect>({name:
   <string>})
   - chrome.tabs.connect(tabId, name) ->
chrome.tabs.connect<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/tabs.html#method-connect>(tabId,
   {name: <string>})
   - chrome.toolstrip.expand(height, url, callback) ->
   
chrome.toolstrip.expand<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/toolstrip.html#method-expand>({height:
   <int>, url: <string>}, callback)
   - chrome.toolstrip.collapse(url, callback) ->
chrome.toolstrip.collapse<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/toolstrip.html#method-collapse>({url:
   <string>}, callback)
   - chrome.windows.getAll(populate, callback) ->
chrome.windows.getAll<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/windows.html#method-getAll>({populate:
   <bool>}, callback)


Changed event name:


   - chrome.bookmarks.onAdded ->
chrome.bookmarks.onCreated<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/bookmarks.html#event-onCreated>

Changed event parameters:


   - chrome.bookmarks.onChildrenReordered(id, childIds) ->
   
chrome.bookmarks.onChildrenReordered<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/bookmarks.html#event-onChildrenReordered>(id,
   {childIds: <array of ints>})
   - chrome.pageAction[<pageActionId>](replyData) ->
chrome.pageAction<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/pageActions.html#H2-1>[<pageActionId>](pageActionId,
   replyData)
   - chrome.windows.onCreated(windowId) ->
chrome.windows.onCreated<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/windows.html#event-onCreated>
   (createInfo)


=================================================

Icons
This isn't a breaking change, but I thought it was worth calling out.

It is now possible to specify icons for your extension. The supported sizes
are: 16, 32, 48, and 128px square. Currently, the extensions system only
uses the 128 size (for the new install dialog), but you are encouraged to
include all four sizes because we will probably be using them more over
time.

More 
information<http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/manifest.html#H3-4>

============================================================

New Developer Tools

Also not a breaking change, but hopefully of interest. The
chrome://extensions/ page has been updated and now includes two tools:


   - "Load unpacked extension": Does the same thing as the --load-extension
   command-line flag, but more convenient than modifying your shortcut.
   - "Pack extension": Does the same thing as the --pack-extension
   command-line flag.


============================================================

That's about it. If I've forgotten anything, I'm sure others will chime in.

Thanks again for all your patience with these changes. We're really excited
to get to this milestone and couldn't have done it without all your feedback
and testing.

If you want to experiment with the new code before the dev release goes out,
you can get a trunk build here:
http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/

- a
*

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to