Development/Languages/Python/PyKDE DBus Tutorial - Revision history

AnneW at 12:31, 18 July 2012

2012-07-18T12:31:34Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:49:58Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:33:47Z
Text replace - "<code python>" to "<syntaxhighlight lang="python">"

				
				
				
				
			
			← Older revision
			Revision as of 20:33, 29 June 2011
			
Line 97:
Line 97:
  First I'm going to throw a whole bunch of code at you. This example contains the basics for setting up a KDE application gui and connecting a button to a dbus method.   First I'm going to throw a whole bunch of code at you. This example contains the basics for setting up a KDE application gui and connecting a button to a dbus method.
    
− <code python> + <syntaxhighlight lang="python">
  #! /usr/bin/python   #! /usr/bin/python
  # -*- coding: utf-8 -*-   # -*- coding: utf-8 -*-
Line 170:
Line 170:
  Now we have imported our libraries, we need to write our main window. In the __init__ (constructor, for the C++ people here) method, we set up the dbus connections:   Now we have imported our libraries, we need to write our main window. In the __init__ (constructor, for the C++ people here) method, we set up the dbus connections:
    
− <code python> + <syntaxhighlight lang="python">
           self.sessionBus = dbus.SessionBus()            self.sessionBus = dbus.SessionBus()
           self.powerdevil = self.sessionBus.get_object('org.freedesktop.PowerManagement',            self.powerdevil = self.sessionBus.get_object('org.freedesktop.PowerManagement',
Line 180:
Line 180:
  ==== Layout and Buttons ====   ==== Layout and Buttons ====
    
− <code python> + <syntaxhighlight lang="python">
           self.layout = QBoxLayout(QBoxLayout.TopToBottom, self)            self.layout = QBoxLayout(QBoxLayout.TopToBottom, self)
           self.setLayout(self.layout)            self.setLayout(self.layout)
Line 198:
Line 198:
  We now need to define the self.screenOff method that we have just connected to the button.   We now need to define the self.screenOff method that we have just connected to the button.
    
− <code python> + <syntaxhighlight lang="python">
       def screenOff(self):        def screenOff(self):
         self.powerdevil.turnOffScreen(dbus_interface='org.kde.PowerDevil')          self.powerdevil.turnOffScreen(dbus_interface='org.kde.PowerDevil')



Astromme at 00:17, 7 April 2009
2009-04-07T00:17:02Z


				
				
				
				
			
			← Older revision
			Revision as of 00:17, 7 April 2009
			
Line 14:
Line 14:
  == Abstract ==   == Abstract ==
    
− The aim of this tutorial is to give an overview of DBus in the context of python. By the end, the goal is to understand how to find DBus methods in existing applications and how to use them in PyQt4/PyKDE4. It assumes a basic working knowledge of Python and PyKDE4. (see ) + The aim of this tutorial is to give an overview of DBus in the context of python. By the end, the goal is to understand how to find DBus methods in existing applications and how to use them in PyQt4/PyKDE4. It assumes a basic working knowledge of Python and PyKDE4.  
    
  === Future Plans ===   === Future Plans ===



Astromme: More table of contents work, small finishing line
2009-04-03T02:20:39Z
More table of contents work, small finishing line

				
				
				
				
			
			← Older revision
			Revision as of 02:20, 3 April 2009
			
Line 11:
Line 11:
  reading=[http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots Qt Signals and Slots in python], [http://www.learningpython.com/2008/09/20/an-introduction-to-pyqt/ Introduction to PyQT4], [http://doc.trolltech.com/intro-to-dbus.html Qt DBus Intro]   reading=[http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots Qt Signals and Slots in python], [http://www.learningpython.com/2008/09/20/an-introduction-to-pyqt/ Introduction to PyQT4], [http://doc.trolltech.com/intro-to-dbus.html Qt DBus Intro]
  }}   }}
−  
− WORK IN PROGRESS  
    
  == Abstract ==   == Abstract ==
Line 161:
Line 159:
       app.exec_ ()        app.exec_ ()
  </code>   </code>
  + 
  + === Walking through the code example ===
  + 
  + ==== Importing Libraries ====
    
  Lets go through this example to try and understand it. First we import the libraries that are needed to make it all work. Most of the Qt and KDE ones should be familiar to you, but to get dbus we need the one at the end: "import dbus".   Lets go through this example to try and understand it. First we import the libraries that are needed to make it all work. Most of the Qt and KDE ones should be familiar to you, but to get dbus we need the one at the end: "import dbus".
  + 
  + ==== DBus Initialization ====
    
  Now we have imported our libraries, we need to write our main window. In the __init__ (constructor, for the C++ people here) method, we set up the dbus connections:   Now we have imported our libraries, we need to write our main window. In the __init__ (constructor, for the C++ people here) method, we set up the dbus connections:
Line 173:
Line 177:
    
  Because the org.freedesktop.PowerManagement is on the Session Bus, we create an object self.sessionBus that represents that bus. We also grab our powerdevil Object via its path /moddules/powerdevil. We can now call methods on the object, but first we need to set up the gui framework, a button and its connection (via Qt signals/slots) to a python method that will call the dbus method.   Because the org.freedesktop.PowerManagement is on the Session Bus, we create an object self.sessionBus that represents that bus. We also grab our powerdevil Object via its path /moddules/powerdevil. We can now call methods on the object, but first we need to set up the gui framework, a button and its connection (via Qt signals/slots) to a python method that will call the dbus method.
  + 
  + ==== Layout and Buttons ====
    
  <code python>   <code python>
Line 187:
Line 193:
    
  If you need help understanding the above, you should consult the reading list linked at the top of this page.   If you need help understanding the above, you should consult the reading list linked at the top of this page.
  + 
  + ==== Calling DBus Methods ====
    
  We now need to define the self.screenOff method that we have just connected to the button.   We now need to define the self.screenOff method that we have just connected to the button.
Line 198:
Line 206:
    
  The rest of the application sets up the KDE app and populates it with author/name info. Again, if you need help with that, see the other reading linked to from the top of this tutorial.   The rest of the application sets up the KDE app and populates it with author/name info. Again, if you need help with that, see the other reading linked to from the top of this tutorial.
  + 
  + Congratulations, you should now have an applet that lets you turn off your screen at the push of a button.



Astromme: Fleshing out the code part of the tutorial
2009-04-03T02:17:28Z
Fleshing out the code part of the tutorial

				
				
				
				
			
			← Older revision
			Revision as of 02:17, 3 April 2009
			
Line 96:
Line 96:
    
  === Code Example ===   === Code Example ===
  + 
  + First I'm going to throw a whole bunch of code at you. This example contains the basics for setting up a KDE application gui and connecting a button to a dbus method.
    
  <code python>   <code python>
Line 159:
Line 161:
       app.exec_ ()        app.exec_ ()
  </code>   </code>
  + 
  + Lets go through this example to try and understand it. First we import the libraries that are needed to make it all work. Most of the Qt and KDE ones should be familiar to you, but to get dbus we need the one at the end: "import dbus".
  + 
  + Now we have imported our libraries, we need to write our main window. In the __init__ (constructor, for the C++ people here) method, we set up the dbus connections:
  + 
  + <code python>
  +         self.sessionBus = dbus.SessionBus()
  +         self.powerdevil = self.sessionBus.get_object('org.freedesktop.PowerManagement',
  +                       '/modules/powerdevil')
  + </code>
  + 
  + Because the org.freedesktop.PowerManagement is on the Session Bus, we create an object self.sessionBus that represents that bus. We also grab our powerdevil Object via its path /moddules/powerdevil. We can now call methods on the object, but first we need to set up the gui framework, a button and its connection (via Qt signals/slots) to a python method that will call the dbus method.
  + 
  + <code python>
  +         self.layout = QBoxLayout(QBoxLayout.TopToBottom, self)
  +         self.setLayout(self.layout)
  + 
  +         label = QLabel ("This is a simple PyKDE4 program", self)
  +         self.layout.addWidget(label)
  +         
  +         button = QPushButton("Push to turn off screen!", self)
  +         self.layout.addWidget(button)
  +         QObject.connect(button, SIGNAL("clicked()"), self.screenOff)
  + </code>
  + 
  + If you need help understanding the above, you should consult the reading list linked at the top of this page.
  + 
  + We now need to define the self.screenOff method that we have just connected to the button.
  + 
  + <code python>
  +     def screenOff(self):
  +       self.powerdevil.turnOffScreen(dbus_interface='org.kde.PowerDevil')
  + </code>
  + 
  + It's relatively simple. We call the method turnOffScreen() on our powerdevil object (the method turnOffScreen was shown on the interface org.kde.PowerDevil in qdbusviewer)
  + 
  + The rest of the application sets up the KDE app and populates it with author/name info. Again, if you need help with that, see the other reading linked to from the top of this tutorial.



Astromme: Cleanups, fix image
2009-04-01T19:06:30Z
Cleanups, fix image

				
				
				
				
			
			← Older revision
			Revision as of 19:06, 1 April 2009
			
Line 26:
Line 26:
  === DBus ===   === DBus ===
    
− First off, a small introduction to DBus. DBus is an inter-process communication framework. In other words, it allows different applications to talk to each other. DBus uses the concept of signals and methods, which are similar to the Signals and Slots in Qt. (For more information on Signals and Slots in python, see http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots) You can connect signals to methods, or call methods directly. + First off, a small introduction to DBus. DBus is an inter-process communication framework. In other words, it allows different applications to talk to each other. DBus uses the concept of signals and methods, which are similar to the Signals and Slots in Qt. (For more information on Signals and Slots in python, suggested reading at the top) You can connect signals to methods, or call methods directly.
    
  === Bus Types ===   === Bus Types ===
Line 70:
Line 70:
    
  Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:   Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:
− [[Image:QDBusViewer-powerdevilpath.png|400px|thumb|left|modules/powerdevil/ path screen]] + [[Image:QDBusViewer-powerdevilPath.png|400px|thumb|left|modules/powerdevil/ path screen]]
    
  === Interfaces ===   === Interfaces ===



Astromme: Added ToC, header info, cheat sheet table
2009-04-01T18:58:32Z
Added ToC, header info, cheat sheet table

				
				
				
				
			
			← Older revision
			Revision as of 18:58, 1 April 2009
			
Line 1:
Line 1:
− The aim of this tutorial is to give an overview of DBus in the context of python. By the end, the goal is to understand how to find DBus methods in existing applications and how to use them in PyQt4/PyKDE4. It assumes a basic working knowledge of Python and PyKDE4. (see http://www.learningpython.com/2008/09/20/an-introduction-to-pyqt/ and http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots) + {{Template:I18n/Language Navigation Bar|Development/Tutorials/Python/PyKDE_DBus_Tutorial}}
  +  
  + {{TutorialBrowser|
  +  
  + series=Python|
  +  
  + name=PyKDE DBus Tutorial|
  +  
  + next=|
  +  
  + reading=[http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots Qt Signals and Slots in python], [http://www.learningpython.com/2008/09/20/an-introduction-to-pyqt/ Introduction to PyQT4], [http://doc.trolltech.com/intro-to-dbus.html Qt DBus Intro]
  + }}
  +  
  + WORK IN PROGRESS
  +  
  + == Abstract ==
  +  
  + The aim of this tutorial is to give an overview of DBus in the context of python. By the end, the goal is to understand how to find DBus methods in existing applications and how to use them in PyQt4/PyKDE4. It assumes a basic working knowledge of Python and PyKDE4. (see )
  +  
  + === Future Plans ===
    
  Later additions to this tutorial may cover creating and emitting dbus signals.   Later additions to this tutorial may cover creating and emitting dbus signals.
    
− ____WORK IN PROGRESS____ + == Introduction ==
  +  
  + === DBus ===
    
  First off, a small introduction to DBus. DBus is an inter-process communication framework. In other words, it allows different applications to talk to each other. DBus uses the concept of signals and methods, which are similar to the Signals and Slots in Qt. (For more information on Signals and Slots in python, see http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots) You can connect signals to methods, or call methods directly.   First off, a small introduction to DBus. DBus is an inter-process communication framework. In other words, it allows different applications to talk to each other. DBus uses the concept of signals and methods, which are similar to the Signals and Slots in Qt. (For more information on Signals and Slots in python, see http://techbase.kde.org/Development/Tutorials/Python_introduction_to_signals_and_slots) You can connect signals to methods, or call methods directly.
  + 
  + === Bus Types ===
    
  Everything sent or received in dbus is transferred over a bus. There are two main buses available, the Session Bus and the System Bus. The former handles per-session (per-user) information while the System Bus handles systemwide notification and settings. For example, the hal subsystem provides a number of interfaces on the System Bus, while Amarok or PowerDevil provides session-specific interfaces for control over music and power options, respectively.   Everything sent or received in dbus is transferred over a bus. There are two main buses available, the Session Bus and the System Bus. The former handles per-session (per-user) information while the System Bus handles systemwide notification and settings. For example, the hal subsystem provides a number of interfaces on the System Bus, while Amarok or PowerDevil provides session-specific interfaces for control over music and power options, respectively.
  + 
  + === Interfaces ===
    
  A DBus path is made up of three parts, the Service Name, the Object Path and the Interface. The following table (taken from the Qt intro to dbus) provides some ways to distinguish between the three parts.   A DBus path is made up of three parts, the Service Name, the Object Path and the Interface. The following table (taken from the Qt intro to dbus) provides some ways to distinguish between the three parts.
    
− TODO: Put in table + === DBus Cheat Sheet ===
− D-Bus Concept +  
− Analogy Name format + {| 
− Service name  Network hostnames  Dot-separated ("looks like a hostname") + |-
−   Object path  URL path component  Slash-separated ("looks like a path") + ! D-Bus Concept !! Analogy !! Name format
−   Interface  Plugin identifier  Dot-separated + |-
  + | Service name || Network hostnames   || Dot-separated ("looks like a hostname")
  + |-
  + | Object path || URL path component   || Slash-separated ("looks like a path")
  + |-
  + | Interface || Plugin identifier   || Dot-separated
  + |}
  +  
  + == Exploring DBus Interfaces ==
    
  One of the easiest ways to discover a DBus method is by browsing for it using qdbusviewer. Run this program from your command line or KRunner (alt+f2) prompt.   One of the easiest ways to discover a DBus method is by browsing for it using qdbusviewer. Run this program from your command line or KRunner (alt+f2) prompt.
  + 
  + === QDBusViewer ===
    
  You should see the following screen:   You should see the following screen:
Line 24:
Line 59:
    
  The two tabs available are the Session Bus and the System Bus.   The two tabs available are the Session Bus and the System Bus.
  + 
  + === Services ===
    
  Within each bus, the left pane shows Service Names. If you click on a service, the right pane shows information about that service.   Within each bus, the left pane shows Service Names. If you click on a service, the right pane shows information about that service.
Line 29:
Line 66:
  Find the org.freedesktop.PowerManagement service and select it. You show now see the following:   Find the org.freedesktop.PowerManagement service and select it. You show now see the following:
  [[Image:QDBusViewer-PowerManagement.png|400px|thumb|left|org.freedesktop.PowerManagement screen]]   [[Image:QDBusViewer-PowerManagement.png|400px|thumb|left|org.freedesktop.PowerManagement screen]]
  + 
  + === Object Paths ===
    
  Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:   Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:
  [[Image:QDBusViewer-powerdevilpath.png|400px|thumb|left|modules/powerdevil/ path screen]]   [[Image:QDBusViewer-powerdevilpath.png|400px|thumb|left|modules/powerdevil/ path screen]]
  + 
  + === Interfaces ===
    
  org.kde.PowerDevil   org.kde.PowerDevil
Line 39:
Line 80:
  The above entries are Interfaces. They are the things that you can actually interact with. When you expand the org.kde.PowerDevil interface, you see a number of Methods and Signals:   The above entries are Interfaces. They are the things that you can actually interact with. When you expand the org.kde.PowerDevil interface, you see a number of Methods and Signals:
  [[Image:QDBusViewer-powerdevilPath-expanded.png|400px|thumb|left|powerdevil expanded screen]]   [[Image:QDBusViewer-powerdevilPath-expanded.png|400px|thumb|left|powerdevil expanded screen]]
  + 
  + === Calling Methods ===
    
  Clicking on a Method will call it. Try clicking on the "turnOffScreen" method. Your screen should go blank. Note: You can get your display back by wiggling your mouse.   Clicking on a Method will call it. Try clicking on the "turnOffScreen" method. Your screen should go blank. Note: You can get your display back by wiggling your mouse.
Line 48:
Line 91:
    
    
− ----------------------------------------------------- + == PyKDE4 ==
    
  Now, for working with methods in python and PyKDE4.   Now, for working with methods in python and PyKDE4.
  + 
  + === Code Example ===
    
  <code python>   <code python>
Line 114:
Line 159:
       app.exec_ ()        app.exec_ ()
  </code>   </code>
−  
−  
−  
−  
− references: http://doc.trolltech.com/intro-to-dbus.html  



Astromme: Added Images and cleaned up python syntax highlighting
2009-04-01T18:37:48Z
Added Images and cleaned up python syntax highlighting

				
				
				
				
			
			← Older revision
			Revision as of 18:37, 1 April 2009
			
Line 21:
Line 21:
    
  You should see the following screen:   You should see the following screen:
− [Insert Initial qdbusviewer screen] + [[Image:QDBusViewer-InitialScreen.png|400px|thumb|left|Initial QDBusViewer Screen]]
    
  The two tabs available are the Session Bus and the System Bus.   The two tabs available are the Session Bus and the System Bus.
Line 28:
Line 28:
    
  Find the org.freedesktop.PowerManagement service and select it. You show now see the following:   Find the org.freedesktop.PowerManagement service and select it. You show now see the following:
− [Insert org.freedesktop.PowerManagement screen] + [[Image:QDBusViewer-PowerManagement.png|400px|thumb|left|org.freedesktop.PowerManagement screen]]
    
  Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:   Everything you see on the right pane is the start of an Object Path. Try expanding down the modules/powerdevil/ path. You should now see the following:
− [Insert modules/powerdevil/ path screen] + [[Image:QDBusViewer-powerdevilpath.png|400px|thumb|left|modules/powerdevil/ path screen]]
    
  org.kde.PowerDevil   org.kde.PowerDevil
Line 38:
Line 38:
    
  The above entries are Interfaces. They are the things that you can actually interact with. When you expand the org.kde.PowerDevil interface, you see a number of Methods and Signals:   The above entries are Interfaces. They are the things that you can actually interact with. When you expand the org.kde.PowerDevil interface, you see a number of Methods and Signals:
− [Insert powerdevil expanded screen] + [[Image:QDBusViewer-powerdevilPath-expanded.png|400px|thumb|left|powerdevil expanded screen]]
    
  Clicking on a Method will call it. Try clicking on the "turnOffScreen" method. Your screen should go blank. Note: You can get your display back by wiggling your mouse.   Clicking on a Method will call it. Try clicking on the "turnOffScreen" method. Your screen should go blank. Note: You can get your display back by wiggling your mouse.
    
  When your display comes back, you should see some information in the bottom pane.   When your display comes back, you should see some information in the bottom pane.
− [Insert turnOffScreen screen] + [[Image:QDBusViewer-turnOffScreen.png|400px|thumb|left|turnOffScreen screen]]
    
  Since the method returned nothing, qdbusviewer told us that.   Since the method returned nothing, qdbusviewer told us that.
Line 52:
Line 52:
  Now, for working with methods in python and PyKDE4.   Now, for working with methods in python and PyKDE4.
    
− [code=python] + <code python>
  #! /usr/bin/python   #! /usr/bin/python
  # -*- coding: utf-8 -*-   # -*- coding: utf-8 -*-
Line 113:
Line 113:
       mainWindow.show ()        mainWindow.show ()
       app.exec_ ()        app.exec_ ()
− [/code] + </code>
    
    



Astromme: Added Python Code
2009-04-01T18:28:43Z
Added Python Code

				
				
				
				
			
			← Older revision
			Revision as of 18:28, 1 April 2009
			
Line 52:
Line 52:
  Now, for working with methods in python and PyKDE4.   Now, for working with methods in python and PyKDE4.
    
  + [code=python]
  + #! /usr/bin/python
  + # -*- coding: utf-8 -*-
  + import sys
  + 
  + from PyKDE4.kdecore import ki18n, KAboutData, KCmdLineArgs
  + from PyKDE4.kdeui import KApplication
  + 
  + from PyQt4.QtGui import QLabel, QWidget, QPushButton, QBoxLayout
  + from PyQt4.QtCore import Qt, QObject, SIGNAL
  + 
  + import dbus
  + 
  + class MainWindow (QWidget):
  +     def __init__ (self):
  +         QWidget.__init__ (self)
  +      
  +         self.sessionBus = dbus.SessionBus()
  +         self.powerdevil = self.sessionBus.get_object('org.freedesktop.PowerManagement',
  +                       '/modules/powerdevil')
  + 
  +         self.layout = QBoxLayout(QBoxLayout.TopToBottom, self)
  +         self.setLayout(self.layout)
  + 
  +         label = QLabel ("This is a simple PyKDE4 program", self)
  +         self.layout.addWidget(label)
  +         
  +         button = QPushButton("Push to turn off screen!", self)
  +         self.layout.addWidget(button)
  + 
  +         QObject.connect(button, SIGNAL("clicked()"), self.screenOff)
  + 
  +         self.resize (640, 480)
  +       
  +     def screenOff(self):
  +       self.powerdevil.turnOffScreen(dbus_interface='org.kde.PowerDevil')
  + 
  + #--------------- main ------------------
  + if __name__ == '__main__':
  + 
  +     appName     = "DBusApp"
  +     catalog     = ""
  +     programName = ki18n ("DBus Example Application")
  +     version     = "1.0"
  +     description = ki18n ("DBus Example")
  +     license     = KAboutData.License_GPL
  +     copyright   = ki18n ("(c) 2009 Andrew Stromme")
  +     text        = ki18n ("none")
  +     homePage    = "http://blog.chatonka.com"
  +     bugEmail    = "astromme@chatonka.com"
  +     
  +     aboutData   = KAboutData (appName, catalog, programName, version, description,
  +                                 license, copyright, text, homePage, bugEmail)
  +     
  +         
  +     KCmdLineArgs.init (sys.argv, aboutData)
  +         
  +     app = KApplication ()
  +     mainWindow = MainWindow ()
  +     mainWindow.show ()
  +     app.exec_ ()
  + [/code]

← Older revision		Revision as of 12:31, 18 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Tutorials/Python/PyKDE_DBus_Tutorial}}~~	+

	{{TutorialBrowser\|		{{TutorialBrowser\|

← Older revision		Revision as of 18:28, 1 April 2009
Line 52:		Line 52:
	Now, for working with methods in python and PyKDE4.		Now, for working with methods in python and PyKDE4.

		+	[code=python]
		+	#! /usr/bin/python
		+	# -- coding: utf-8 --
		+	import sys
		+
		+	from PyKDE4.kdecore import ki18n, KAboutData, KCmdLineArgs
		+	from PyKDE4.kdeui import KApplication
		+
		+	from PyQt4.QtGui import QLabel, QWidget, QPushButton, QBoxLayout
		+	from PyQt4.QtCore import Qt, QObject, SIGNAL
		+
		+	import dbus
		+
		+	class MainWindow (QWidget):
		+	def __init__ (self):
		+	QWidget.__init__ (self)
		+
		+	self.sessionBus = dbus.SessionBus()
		+	self.powerdevil = self.sessionBus.get_object('org.freedesktop.PowerManagement',
		+	'/modules/powerdevil')
		+
		+	self.layout = QBoxLayout(QBoxLayout.TopToBottom, self)
		+	self.setLayout(self.layout)
		+
		+	label = QLabel ("This is a simple PyKDE4 program", self)
		+	self.layout.addWidget(label)
		+
		+	button = QPushButton("Push to turn off screen!", self)
		+	self.layout.addWidget(button)
		+
		+	QObject.connect(button, SIGNAL("clicked()"), self.screenOff)
		+
		+	self.resize (640, 480)
		+
		+	def screenOff(self):
		+	self.powerdevil.turnOffScreen(dbus_interface='org.kde.PowerDevil')
		+
		+	#--------------- main ------------------
		+	if __name__ == '__main__':
		+
		+	appName = "DBusApp"
		+	catalog = ""
		+	programName = ki18n ("DBus Example Application")
		+	version = "1.0"
		+	description = ki18n ("DBus Example")
		+	license = KAboutData.License_GPL
		+	copyright = ki18n ("(c) 2009 Andrew Stromme")
		+	text = ki18n ("none")
		+	homePage = "http://blog.chatonka.com"
		+	bugEmail = "astromme@chatonka.com"
		+
		+	aboutData = KAboutData (appName, catalog, programName, version, description,
		+	license, copyright, text, homePage, bugEmail)
		+
		+
		+	KCmdLineArgs.init (sys.argv, aboutData)
		+
		+	app = KApplication ()
		+	mainWindow = MainWindow ()
		+	mainWindow.show ()
		+	app.exec_ ()
		+	[/code]