summaryrefslogtreecommitdiffstats
path: root/kopete/plugins/nowlistening/DESIGN
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-02-01 15:14:03 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-02-01 15:14:03 -0600
commit9c9412b30c54468adc9e506cc76c5d113fbf5056 (patch)
tree68a0c0d5bc770fc58596b8c5624cdf33d8625027 /kopete/plugins/nowlistening/DESIGN
parent2e53bd0b77676f879fad7baeecea5879bf496a7d (diff)
downloadtdenetwork-9c9412b30c54468adc9e506cc76c5d113fbf5056.tar.gz
tdenetwork-9c9412b30c54468adc9e506cc76c5d113fbf5056.zip
Rename a number of classes to enhance compatibility with KDE4
Diffstat (limited to 'kopete/plugins/nowlistening/DESIGN')
-rw-r--r--kopete/plugins/nowlistening/DESIGN2
1 files changed, 1 insertions, 1 deletions
diff --git a/kopete/plugins/nowlistening/DESIGN b/kopete/plugins/nowlistening/DESIGN
index d2be5d5f..1cfb105b 100644
--- a/kopete/plugins/nowlistening/DESIGN
+++ b/kopete/plugins/nowlistening/DESIGN
@@ -36,7 +36,7 @@ How contact specific plugin data works
Each metacontact has a method pluginData(KopetePlugin *). This takes a pointer to a plugin, and returns a QStringList containing the metacontact's data for that plugin. A corresponding setPluginData() method changes this. Who is responsible for making sure this data persists?
What about custom actions?
-KopetePlugin::custom[Chat|ContextMenuActions] both return a set of KActions that the plugin wants to have added to the UI. Looking at contactnotes, it seems that this set is recreated every time thses methods are called and they change the state of the plugin (currentContact). Is this so that the context menu is generated individually for each MC, so that the method that is called when the men item is clicked know which MC it applies to?
+KopetePlugin::custom[Chat|ContextMenuActions] both return a set of TDEActions that the plugin wants to have added to the UI. Looking at contactnotes, it seems that this set is recreated every time thses methods are called and they change the state of the plugin (currentContact). Is this so that the context menu is generated individually for each MC, so that the method that is called when the men item is clicked know which MC it applies to?
Choosing whether to advertise to all contacts
We can either advertise periodically to (some) contacts, or we could just add an Action to advertise what we're currently listening to.