525
edits
Talk:Bookmarks Data API: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
The "type" field is intended to identify the provider type, but it probably should just be a pointer to a bmIBookmarkProvider. There's a few comment bugs I'll fix shortly as well -- the bookmark provider's name property should say "as displayed in the UI", not URI, and the comment about |getBookmarkByType| should instead be talking about |getKnownBookmark| (I realized that "type" was way too overloaded). One case I'd like to handle is where a certain bookmark type was being handled by an extension, but the user disabled/uninstalled that extension. I don't think we should lose those particular bookmarks, though maybe we just won't display them. I also might ditch the whole string serialization/deserialization bit, and just require all providers to store whatever extra data they have in each node's property bag, and just serialize that way directly to storage. --[[User:VladVukicevic|VladVukicevic]] 12:46, 6 Jul 2005 (PDT) | The "type" field is intended to identify the provider type, but it probably should just be a pointer to a bmIBookmarkProvider. There's a few comment bugs I'll fix shortly as well -- the bookmark provider's name property should say "as displayed in the UI", not URI, and the comment about |getBookmarkByType| should instead be talking about |getKnownBookmark| (I realized that "type" was way too overloaded). One case I'd like to handle is where a certain bookmark type was being handled by an extension, but the user disabled/uninstalled that extension. I don't think we should lose those particular bookmarks, though maybe we just won't display them. I also might ditch the whole string serialization/deserialization bit, and just require all providers to store whatever extra data they have in each node's property bag, and just serialize that way directly to storage. --[[User:VladVukicevic|VladVukicevic]] 12:46, 6 Jul 2005 (PDT) | ||
Another thought - if I want to be able to build a single view to manage Bookmarks and History and perhaps other datasources (e.g. Bonjour) does this provide a mechanism to talk about containment? Is that what bmIBookmarkProvider is? (are History/Bonjour Bookmark Providers?) it was not clear if the contents supplied by Bookmark Providers was serialized into the Bookmarks Datasource... the Livemark example doesn't really illuminate because presently livemark content is serialized into bookmarks.html. --[[User:Ben|Ben]] 15:37, 6 Jul 2005 (PDT) | |||