> History > APIs to the built-in history and bookmark system. For example, > to be notified when the star button is pressed, or to > push items into either database
The routine that I followed differed slightly from the routine specified in the Chrome Extension HOWTO, and it wasn't clear that I had to exit then re-run with extensions (a second time) for the installation to be effective, my annotations are at http://www.diigo.com/user/grahamperrin/Chrome+Diigolet
Please, do you have a reference?
http://dev.chromium.org/developers/design-documents/extensions/extension-manifesto
> Goals
> … only one extension system in Chromium that handles all types of extensibility
> … traditional NPAPI plugins should be deployable as extensions
http://dev.chromium.org/developers/design-documents/extensions/process-model
http://dev.chromium.org/system/app/pages/search?q=xpi
- xpi not found
http://dev.chromium.org/developers/design-documents/multi-process-architecture
> Firefox-style NPAPI plug-ins run in their own process, separate from renderers.
> This is described in detail in Plugin Architecture.
http://dev.chromium.org/developers/design-documents/plugin-architecture
http://dev.chromium.org/developers/design-documents/extensions/apiwishlist - in the wish list, amongst the areas that developers are not yet working on:
> Content layers
> Shelves and bottom bars
> Sidebars
> Pop-out areas
> Read-only user scripts
> Read-write user scripts
> History
> APIs to the built-in history and bookmark system. For example,
> to be notified when the star button is pressed, or to
> push items into either database
This feature is marked "implemented and ready-to-roll".
Cleeki for Chrome uses this method: http://blog.cleeki.com/?p=112 and works great.
Hope this helps... can't wait for Diigo on Chrome!
Jean-Lou.
http://code.google.com/p/chrome-diigo/
Diigo is loaded but somehow the javascript console spews some exception code to the effect that 'diigolet is not defined'.
Maybe the Diigo team would like to try it out?
Anyhow, it's a start.
Jean-Lou.
The routine that I followed differed slightly from the routine specified in the Chrome Extension HOWTO, and it wasn't clear that I had to exit then re-run with extensions (a second time) for the installation to be effective, my annotations are at http://www.diigo.com/user/grahamperrin/Chrome+Diigolet
The results of initial tests lead nicely into another topic:
http://groups.diigo.com/Diigo_HQ/forum/topic/keep-diigolet-active-299#4