said E. Liddell: | If it's a true plugin, it probably doesn't *have* a separate executable. | Plugins are sort of like the inverse of libraries: they implement some | sort of interface or contract provided by the host program. The kipi | plugins appear to implement a common interface used by multiple TDE | graphics programs. I considered that possibility, but there has to be some way to invoke it. | Unless you can figure out how to use DCOP to send a message to gwenview | that will force-invoke the plugin, or you're willing to write some kind | of kipi stub-invoker, I suspect you're out of luck here. Do you think that the code in the actual menu entry contains all that code? Because all I hope to do it copy it from one menu on Gwenview to another menu in Gwenview, the latter being a freely editable one. It's not as if I want it to run free-standing, or to open it in a different program. Juast literally move it from one menu to another. Something that also puzzled me a little is that there is a kipiplugin.metadataedit.desktop file (in /opt/trinity/share/services). Beyond listing every language spoken in the solar system and nearby parts of the galaxy, it has this: X-TDE-ServiceTypes=KIPI/Plugin Type=Service X-TDE-Library=kipiplugin_metadataedit Which I'm sure means something, though I know not what, beyond the extremely obvious. -- dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://www.athensnews.com/opinion/columns/the_view_from_mudsock_heights/ ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
