KDE Utils/kdelirc: Difference between revisions
Created page with '== kdelirc Plans == === KDE 4.4 === See the feature plan for KDE 4.4. * Communicate to lirc through solid === Long time goals / id...' |
m 9 revisions imported: imported from techbase |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
* Communicate to lirc through solid | * Communicate to lirc through solid | ||
* Integrate solid backend into kdelirc frontend | |||
* Cycle mode function (see [https://bugs.kde.org/show_bug.cgi?id=134060 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 ==== | ==== Backend ==== | ||
* Provide plasma data engine | * Provide plasma data engine | ||
* Multi application profiles | * 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: | |||
< | <syntaxhighlight lang="text"> | ||
VolumeSet(VolumeGet() + 10); | |||
</syntaxhighlight> | |||
It should be something like: | 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> | ||
</syntaxhighlight> | |||
==== Frontend ==== | ==== Frontend ==== | ||
* Merge add action and edit action dialog into one dialog | * Merge add action and edit action dialog into one dialog | ||
* KNewStuff for profiles | |||
Latest revision as of 10:27, 15 April 2016
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);
It should be something like:
<action objid="Player" class="volumeup">
<name>Increase volume</name>
<comment></comment>
<someNewTagName>
VolumeSet(VolumeGet() + 10);
</someNewTagName>
</action>
Frontend
- Merge add action and edit action dialog into one dialog
- KNewStuff for profiles