Rekonq reports the open/close document events to activity manager daemon.

By knowing which window contains which documents and which one is in
focus, we can do the following:

- collect the statistics about visited pages. Further, this provides a
score for each document visited, that depends on the number of times it
was open, the time the user spent on that location, and the time passed
since the last visit.
- availability of a global/workspace applet that allows sharing the
current document via e-mail, social networks; bookmarking and rating the
link, or connecting it to the current activity. (advantage of this is a
        unified UI for sharing/rating/linking that works with any
        application)
- jump-lists (not impl. yet in plasma) to list top rated documents on a
launcher icon or in the task manager applet
- krunner can sort the documents based on the score
- more things that I haven't thought of yet

There is no need to *use* ativities to have these benefits. Activities
just serve as manual data clustering to provide more useful scores
compared to the one-activity approach.

REVIEW:106912

1 files changed, 12 insertions, 0 deletions

diff --git a/src/mainview.h b/src/mainview.h
index 89ee36ec..d8547530 100644
--- a/src/mainview.h
+++ b/src/mainview.h
@@ -38,18 +38,26 @@
 // KDE Includes
 #include <KTabWidget>
 
+// Config
+#include <config-kactivities.h>
+
 // Forward Declarations
 class MainWindow;
 class StackedUrlBar;
 class TabBar;
 class UrlBar;
 class WebTab;
+class WebView;
 
 class QLabel;
 class QToolButton;
 class QUrl;
 class QWebFrame;
 
+#ifdef HAVE_KACTIVITIES
+namespace KActivities { class ResourceInstance; }
+#endif
+
 
 /**
  * This class represent rekonq Main View.
@@ -194,6 +202,10 @@ private:
     int m_currentTabIndex;
 
     QList<TabHistory> m_recentlyClosedTabs;
+
+#ifdef HAVE_KACTIVITIES
+    KActivities::ResourceInstance * activityResourceInstance(WebView * view);
+#endif
 };
 
 #endif // MAINVIEW_H