Scripted KParts-Plugins

[David Palacio]

2010/4/19 Jonathan Schmidt-Dominé - Developer <devel at the-user.org>:
> Hi!
>
> I fixed KParts::Plugin (PluginKeyword was missing, don't worry, it seems to be
> binary compatible) and now scripted KParts-Plugins work. Such plugins could be
> used in Konqueror for the whole app (see attachments, a ruby- and a python-
> plugin), dolphinpart or khtmlpart, although dolphinpart is limited, because it
> does not have a public API. How do you think about it? Do you think it would
> be useful to integrate KHNS into Konqueror for such scripted plugins? I think
> some templates would be a good second step.
>
> Jonathan
>
> ------------------------
> Operating System: GNU/Linux
> Kernel: Linux 2.6.31.8-0.1-default
> Distribution: openSuSE 11.2
> Qt: 4.6.3
> KDE: 4.4.72 (KDE 4.4.72 (KDE 4.5 >= 20100415)) "release 4"
> KMail: 1.13.2
> http://gnu.org/
> http://kde.org/
> http://windows7sins.org/
>
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings
>
>

Hi,

I tried this for a while and found a problem in kdelibs. When a plugin
is disabled/enabled, an entry under [KParts Plugins] named
pluginNameEnabled is added. If that entry exists, the plugin keyword
entry, critical for Ruby plugins, is not read. See
kdelibs/kparts/plugin.cpp:265. This affects all KParts plugins.

Also, do you get a non-nil parent for your ruby_konqueror_plugin
instance? I get nil here.
_______________________________________________
Kde-bindings mailing list
Kde-bindings at kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings