Difference between revisions of "Development/Tutorials/Kross/Scripts-as-KPlugins"

(Just a link)
 
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
  
Once you have successfully [Development/Tutorials/Kross/Scripts-as-Plugins created a working Plugin with Kross] for your application, you probably would like to have it recognized as a KPlugin, so that you can retrieve it through KService. Doing that is easy and does not require additional compiled code: you just need to create a wrapper KPlugin and a service descriptor (.desktop) file for your script, just as if it was a real C++ Plugin.
+
Once you have successfully [[Development/Tutorials/Kross/Scripts-as-Plugins|created a working Plugin with Kross]] for your application, you probably would like to have it recognized as a KPlugin, so that you can retrieve it through KService. Doing that is easy and does not require additional compiled code: you just need to create a wrapper KPlugin and a service descriptor (.desktop) file for your script, just as if it was a real C++ Plugin.
  
 
The real part is coming soon.
 
The real part is coming soon.

Latest revision as of 15:28, 4 May 2008

Introduction

Once you have successfully created a working Plugin with Kross for your application, you probably would like to have it recognized as a KPlugin, so that you can retrieve it through KService. Doing that is easy and does not require additional compiled code: you just need to create a wrapper KPlugin and a service descriptor (.desktop) file for your script, just as if it was a real C++ Plugin.

The real part is coming soon.


This page was last edited on 4 May 2008, at 15:28. Content is available under Creative Commons License SA 4.0 unless otherwise noted.