simon

Hi Peter, Now for something a little more advanced... Rythmbox is the default music player in Fedora FC12. In trying to understand how Simon works I would like to see how far I can get in controlling Rythmbox. Rythmbox has a command line interface called rythmbox-client, which has the following commands: Application Options: --debug --no-start Don't start a new instance of Rhythmbox --quit Quit Rhythmbox --no-present Don't present an existing Rhythmbox window --hide Hide the Rhythmbox window --next Jump to next song --previous Jump to previous song --notify Show notification of the playing song --play Resume playback if currently paused --pause Pause playback if currently playing --play-pause Toggle play/pause mode --play-uri=URI to play Play a specified URI, importing it if necessary --enqueue Add specified tracks to the play queue --clear-queue Empty the play queue before adding new tracks --print-playing Print the title and artist of the playing song --print-playing-format Print formatted details of the song --set-volume Set the playback volume --volume-up Increase the playback volume --volume-down Decrease the playback volume --print-volume Print the current playback volume --mute Mute playback --unmute Unmute playback --set-rating Set the rating of the current song Now, I could use the 'Program' plugin, with 'music' as the trigger, and have a manual command for each rythmbox command, e.g. for 'pause' have a command 'rythmbox-client --pause', and assign it to a command trigger called 'pause' But it seems like it should be a plugin (like calculator) with the command as an 'action' - is that something that can be easily done? thanks, Ken

Hi! Well you could write a plugin if you wanted but why not create program commands? Maintaining a separate plugin for rythmbox seems rather unnecessary to me... If you have something specific in mind pease provide a mockup describing your proposed plugin. If you want to make it easier for other users to control rythmbox you could create a scenario and publish it on kde-files.org. Greetings, Peter

>Well you could write a plugin if you wanted but why not create program commands? I forgot about scenarios, even though it is the second selection on the menu... >Maintaining a separate plugin for rythmbox seems rather unnecessary to me... that is all I need to know - scenarios work for me >If you want to make it easier for other users to control rythmbox you could create a scenario and publish it on kde-files.org. Done. Here is the link: http://kde-files.org/content/show.php/Rythmbox-simon?content=124456&PHPSESSID=6874b6ada5a20eea18efe2be819269da Ken

Our first user contributed scenario! :) Just a few ideas: I tried to establish a naming convention for the uploads to kde files: "[<language code>/<compatible basemodel (if any)>]". In your case this would become: "[EN/VF]". To make it easier for new users who don't use a base model you could add a trainings text with your vocabulary (Training > Add). If you want to polish your submission a little you could also set the icon to the rythmbox icon (of the scenario as well as the submission on kde-files) and add a little description (on kde-files). Sorry for being so nitpicky but as this is one of the early submissions I really want to keep the quality of the scenario repository as high as possible for as long as possible :) Greetings, Peter Ps.: What do you think of the scenario system?

Thanks for updating the scenario!