On Mon, Jun 15, 2009 at 1:25 PM, Colin Bleckner <[email protected]>wrote:
> Thanks for the details! I'm a little surprised that bookmark IDs > aren't persistent. Out of curiosity, do you know why that decision > was made? I believe it's simply because it wasn't necessary. Some people have large numbers of bookmarks, so every field we added to the storage slows down import, load and save. It's possible we'll reconsider this in the not-too-distant future. I'm merely reporting the state of the universe as it exists now. ;-) > I'm also (happily!) surprised to hear you'd consider allowing data to > be added to the bookmark itself. I figured the answer was going to be > "use the bookmark id and local storage to store stuff." :) I'll put > in a feature request this afternoon. Well, without persistent bookmark id's, that wouldn't work. ;-) Just so you don't get your hopes up on this front, while I think that this is reasonable, it's possible that others won't, so this is by no means guaranteed. Once you file the feature request, you'll be able to track those decisions as we make them though. Erik > > > Colin > > > > On Fri, Jun 12, 2009 at 11:12 AM, Erik Kay<[email protected]> wrote: > > On Fri, Jun 12, 2009 at 10:48 AM, Colin <[email protected]> wrote: > >> > >> I've been playing with the bookmarks API for a day or so and so far > >> things are great. It's simple and very easy to use (aside from a few > >> inconsistencies in the API that are already addressed in a couple of > >> open bugs). I do have a couple of questions, though. > > > > Glad to hear it! > > > >> > >> I haven't seen this mentioned anywhere, is a bookmark's ID guaranteed > >> to remain the same through its lifespan? As its moved around, > >> updated, and Chrome is closed and restarted, will a bookmark keep the > >> same ID? > > > > A bookmark id is only guaranteed to be unique for the session. Do not > > persist it. Sorry the docs are quite minimal at the moment. I'll add > this > > point. > > > >> > >> Currently we only have access to a very small amount of information > >> about each bookmark. Are there plans to add access other data such as > >> create date, modified date, the favicon, etc? > > > > Yes. We'll be adding the create date and the modified date. I looked > > around, and realized we don't have a bug for this, so I filed one: > > http://code.google.com/p/chromium/issues/detail?id=13994 > > Favicon is a bit more complex because it's stored independently of the > > bookmark system and the underlying mechanism will be changing > significantly > > soon. We hope to be able to support favicons generically in extensions, > in > > a way not specific to bookmarks, but there are no specific plans here > yet. > > > >> > >> Are there any plans to allow developers to add custom fields to store > >> additional data inside a bookmark? For example, if I wanted to create > >> an extension that added tags and a description to Chrome's bookmarks, > >> would I be able to shove that data into the bookmark itself somehow? > > > > Not at the moment, but this is a reasonable request. Could you please > file > > a feature request for this with a bit more details about the specific use > > cases you'd like to see supported? > > > > Erik > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
