Hello, > Hello! > > Yes, I didn't polish enough the new konqueror bookmarks enough to make > it into 4.4 either, but I'll try hard to move it into KDE SC 4.5. We > can work on this dataengine together ;-). You can see the current > state of the new bookmarks system in http://github.com/edulix/gsoc/, > and we can see how to deal with them in the dataengine. To do this I have to learn a bit about the Akonadi programming... If I understand you right, we would use the Akonadi resource as source for the Konqueror bookmarks? > I don't understand very well what you're trying to do with the > num-name num-bookmark. Is it to avoid bookmark duplication because of > having multiple bookmarks providers? If so, maybe you should also take > into account then also history in that dataengine, because it's quite > likely users actually visit their bookmarks, so even if the bookmarks > are not duplicated in the dataengine, there will duplicated entries: > one for the bookmark runner, the other for the history runner. There > should probably be instead something like a "web browser" runner which > unifies both runners and is configurable to search in history, > bookmarks, or both (?). I'm new to dataengine programming so I hope my thoughts where right: A dataengine has got different sources. The sources in this case are the browsers like Konqueror and Firefox. The entries in one source are things like QString or QUrl. But a bookmark has got two things to share: the name and the url. So I use two things for one bookmark: QUrl 1-url with the value http://forum.kde.org QString 1-name with the value KDE Forum And another bookmark would have these entries: QUrl 2-url with the value http://kde.org QString 2-name with the value KDE Homepage
I'm afraid that this isn't the best solution...correct me if I'm wrong. Greetings, Jan Gerrit Marker (jangmarker) _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
