Projects/Utils/kdelirc - Revision history

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:39Z

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

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


2011-06-29T20:44:56Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:44, 29 June 2011
			
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>



Neverendingo: Text replace - "" to ""

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

				
				
				
				
			
			← Older revision
			Revision as of 20:33, 29 June 2011
			
Line 18:
Line 18:
  </code>   </code>
     It should be something like:      It should be something like:
− <code xml> + <syntaxhighlight lang="xml">
  <action objid="Player" class="volumeup">   <action objid="Player" class="volumeup">
     <name>Increase volume</name>      <name>Increase volume</name>



Frasche at 11:58, 27 October 2009
2009-10-27T11:58:21Z


				
				
				
				
			
			← Older revision
			Revision as of 11:58, 27 October 2009
			
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 ===   === 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.   In this section are some ideas  and features listened, were discussing about. Maybe these will be implemented in a further release of kdelirc.



Frasche at 19:14, 11 September 2009
2009-09-11T19:14:41Z


				
				
				
				
			
			← Older revision
			Revision as of 19:14, 11 September 2009
			
Line 14:
Line 14:
    
  <code>   <code>
−  VolumeSet(VolumeGet() + 10); + VolumeSet(VolumeGet() + 10);
  </code>   </code>
     It should be something like:      It should be something like:
  <code xml>   <code xml>
−     <action objid="Player" class="volumeup"> + <action objid="Player" class="volumeup">
−         <name>Increase volume</name> +   <name>Increase volume</name>
−         <comment></comment> +    <comment></comment>
−         <someNewTagName> +    <someNewTagName>
−           VolumeSet(VolumeGet() + 10); +       VolumeSet(VolumeGet() + 10);
−         </someNewTagName> +     </someNewTagName>
−     </action> + </action>
  </code>   </code>
  ==== 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   * KNewStuff for profiles



Tampakrap at 19:09, 11 September 2009
2009-09-11T19:09:56Z


				
				
				
				
			
			← Older revision
			Revision as of 19:09, 11 September 2009
			
Line 28:
Line 28:
  ==== 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



Tampakrap at 18:52, 11 September 2009
2009-09-11T18:52:55Z


				
				
				
				
			
			← Older revision
			Revision as of 18:52, 11 September 2009
			
Line 6:
Line 6:
    
  === Long time goals / ideas ===   === 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
Line 11:
Line 13:
  * 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 xml n> + <code>
    VolumeSet(VolumeGet() + 10);     VolumeSet(VolumeGet() + 10);
  + </code>
     It should be something like:      It should be something like:
  + <code xml>
       <action objid="Player" class="volumeup">        <action objid="Player" class="volumeup">
           <name>Increase volume</name>            <name>Increase volume</name>



Tampakrap at 18:44, 11 September 2009
2009-09-11T18:44:57Z


				
				
				
				
			
			← Older revision
			Revision as of 18:44, 11 September 2009
			
Line 9:
Line 9:
  * 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: + * 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 xml n>   <code xml n>



Tampakrap: 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...'
2009-09-11T18:44:03Z
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...'
New page
== kdelirc Plans ==

=== KDE 4.4 ===

See the [[Schedules/KDE4/4.4_Feature_Plan#kdeutils|feature plan]] for KDE 4.4.



* Communicate to lirc through solid 



=== Long time goals / ideas ===

==== 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:



<code xml n>

 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>

</code>

==== Frontend ====

* Merge add action and edit action dialog into one dialog

← Older revision		Revision as of 19:09, 11 September 2009
Line 28:		Line 28:
	==== 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