Difference between revisions of "Projects/Utils/kdelirc"

Jump to: navigation, search
m (Text replace - "<code xml>" to "<syntaxhighlight lang="xml">")
m (Text replace - "<code>" to "<syntaxhighlight lang="text">")
Line 14: Line 14:
 
* Look for a way to do more complex action into profile not calling only one simple dbus method.  At moment we can't do something like increase volume on amarok because we need to do something like:
 
* Look for a way to do more complex action into profile not calling only one simple dbus method.  At moment we can't do something like increase volume on amarok because we need to do something like:
  
<code>
+
<syntaxhighlight lang="text">
 
VolumeSet(VolumeGet() + 10);
 
VolumeSet(VolumeGet() + 10);
 
</code>
 
</code>

Revision as of 21:44, 29 June 2011

Contents

kdelirc Plans

KDE 4.4

See the feature plan for KDE 4.4.

  • Communicate to lirc through solid
  • Integrate solid backend into kdelirc frontend
  • Cycle mode function (see Bug 134060)

Long time goals / ideas

In this section are some ideas and features listened, were discussing about. Maybe these will be implemented in a further release of kdelirc.

Backend

  • Provide plasma data engine
  • Multi application profiles
  • Look for a way to do more complex action into profile not calling only one simple dbus method. At moment we can't do something like increase volume on amarok because we need to do something like:
VolumeSet(VolumeGet() + 10);
</code>
  It should be something like:
<syntaxhighlight lang="xml">
<action objid="Player" class="volumeup">
  <name>Increase volume</name>
   <comment></comment>
   <someNewTagName>
      VolumeSet(VolumeGet() + 10);
    </someNewTagName>
</action>
</code>
==== Frontend ====
* Merge add action and edit action dialog into one dialog
* KNewStuff for profiles

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