On Sun, Sep 29, 2013 at 10:31 PM, Sebastian Kügler <se...@kde.org> wrote:
> On Sunday, September 29, 2013 20:50:28 David Faure wrote: > > This is clearly because kbookmarks was written as part of kio, and with > > konqueror in mind. I guess the question is how generic we want KBookmarks > > to be, i.e. should it work without KIO altogether (at the expense of > > losing automatic favicon integration -- can still be done by the caller > > though, as long as the favicon doesn't change over time... as far as I > can > > see from the code). > > Maybe KBookmark could just be a small API backed by plugins? > > This would allow us to tackle bookmark provision "the other way round", so > we > could > > - use different providers, thereby hook into what's there on a given system > - use Nepomuk as a backend (we use Nepomuk for browser bookmarks in Plasma > Active > - hook into Chrome and Firefox bookmarks (at least read-only), we have code > for this in KRunner > - it'd let us get away for KBookmarks itself with minimal dependencies > > I imagine KBookmark being a more service-like thing, rather than a > mechanism > to store and read bookmarks. > > Hi Sebas, If i'm not mistaken, Dolphin is also using KBookmarks. Would your suggestion keep it alive for dolphin? Or would that mean creating a plugin that can read/write bookmarks to any file? Cheers, Mark
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
