[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 72010] Context menu plugin system like KonqPopupMenuPlugin,
From:       Don Sanders <sanders () kde ! org>
Date:       2004-01-09 1:37:57
Message-ID: 20040109013757.27017.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=72010      




------- Additional Comments From sanders@kde.org  2004-01-09 02:37 -------
Subject: Re:  Context menu plugin system like KonqPopupMenuPlugin, Please

One idea that I can't get out of my head it using a combination of 
KPlugin, XMLGUI, and DCOP to provide pluggable functionality.

Currently we don't use XMLGUI for the context menu but we could, and 
it does make some sense. (I mean in the appropriate.rc file you can 
list KActions that should appear for the readerwindow and 
messageheaders contextmenu).

KPlugin could be used to load modules that create new KActions. So I 
could modify my .rc, add a new readerwindow context menu item 
KAction, write a KPlugin that implements this KAction and then put 
this KPlugin in some predefined directory. KMail/Kontact will load 
all plugins in this directory at start up.

The plugins could talk to KMail or other components via their dcop 
interfaces (maybe via a wrapper library rather than directly). 
Possibly using private dcop interfaces KActions like remove duplicate 
messages could be moved out of the core KMail code into a plugin 
directory, as time goes on maybe some private dcop interfaces could 
mature into public ones.

In the long run I kind of have a mental picture of gimp like plugins 
for Kontact, where organizations can implement specialized 
functionality to suit their communication needs. Only unlike gimp 
plugins the basic gui (Menus, toolbars, context menus) could be 
changed.

Maybe these plugins could be programmed in a high level language like 
python or ruby.

Don.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]