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

Reply via email to