On Apr 14, 2011, at 11:06 AM, Patrick Robertson wrote: > Looks like the Chrome Bookmarks are stored in a .json file, which means the > plugin would just need to open up the file (App > Support/Google/Chrome/Default/Bookmarks for me) use a .json parser (I use > JSON Framework in my 1Password plugin) then make them URLs.
Notes for the mythical Google Chrome Plug-in developer: I was thinking a proper browser plug-in would also provide access to history and a proxy object referring to “the URL of the page I’m currently looking at”. Looking at the AppleScript support in Chrome to see if the proxy object would be possible (I think it would), I noticed some references to “bookmark item”. On the one hand, it might be safer to get a list of bookmarks via AppleScript, so if the internal format ever changes, it still works. On the other hand, that only works if Chrome is running, which is not ideal. Personally, I think it’s worth the risk to go to the JSON file directly. Anyone know what happens if you use the service that syncs bookmarks? Things to check for would be: 1. Does the browser still store them locally at all, or does it just rely on the remote info? 2. Does it still use “Default”, or does it create a new folder based on your Google Account? Have fun, mythical developer! :) -- Rob McBroom <http://www.skurfer.com/>
