Difference between revisions of "Development/Tutorials/Plasma/Services"

Jump to: navigation, search
(Starts to put some content)
Line 17: Line 17:
  
 
cover services, .operations file, .operations dtd spec, perhaps make a service like the pastebin one or something. idk, something easy.  
 
cover services, .operations file, .operations dtd spec, perhaps make a service like the pastebin one or something. idk, something easy.  
 +
 +
http://www.kde.org/standards/kcfg/1.0/kcfg.xsd
  
 
also mention how a service can access the dataengine via it's pointer(I think that's in public api), if it really really needs to(e.g. plasma-kdm can't live without that)
 
also mention how a service can access the dataengine via it's pointer(I think that's in public api), if it really really needs to(e.g. plasma-kdm can't live without that)

Revision as of 04:04, 26 January 2011


Development/Tutorials/Plasma/DataEngines


Writing a Data Engine
Tutorial Series   Plasma Tutorial
Previous   C++, Qt, KDE4 development environment
What's Next  
Further Reading   DataEngine API, CMake Tutorials, Writing a Plasmoid (Tutorial)

Abstract

cover services, .operations file, .operations dtd spec, perhaps make a service like the pastebin one or something. idk, something easy.

http://www.kde.org/standards/kcfg/1.0/kcfg.xsd

also mention how a service can access the dataengine via it's pointer(I think that's in public api), if it really really needs to(e.g. plasma-kdm can't live without that)

The Plasma Engine Explorer

A very useful tool for anyone writing services is the Plasma engine explorer. You can use it to see test services by launching them by running

plasmaengineexplorer

If the service you want to test is associated to a source, you can access a dialog to launch the service and set its parameters

Plasma-engine-explorer-task-service.png


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal