Description: This script simply provides a shortcut for starting AmarokFS ("Amarok Full Screen") from within Amarok itself.
AmarokFS itself can be downloaded from: http://www.kde-apps.org/content/show.php?content=52641
Installation: Download the .amarokscript.tar file and install it with Amarok's script installer.
Usage: Upon startup, the script will automatically look for the "amarokFS" executable in your PATH, and if not found, will prompt you for its location. Once the script is running, you will have an "AmarokFS" menu entry in your playlist popup menu; now simply select "Run Amarok Full Screen" to activate AmarokFS.
The script can also be configured to use an amarokFS executable other than the one detected in the user's PATH.
Dependencies: Amarok AmarokFS Python kdialog
Author: Francois Aucamp
License: This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.Last changelog:
* Thu Mar 29 2007 Francois Aucamp - 1.1 - Added multi-head patch by Martin Kossler - Added "configure" modification by Martin Kossler - Added script dependency checking
* Mon Feb 12 2007 Francois Aucamp - 1.0 - Created AmarokFS script for Fedora "amarokFS" package
As I know, if users use scim, when they type command in kdialog, it would be like this in config file:
ScimInputContextPlugin()
QMultiInputContext::changeInputMethod(): index=0, slave=scim
~ScimInputContextPlugin()
Maybe in this section, the code:
cmd=commands.getoutput('kdialog --inputbox "xxxxxx" 2>/dev/null')
would be better.
The other some-function script has this problem too,but it is finall version.
First, nice job on this script. It works perfectly. What I would like is either a toolbar button or a shortcut key that would turn on/off your script. Not sure if that is possible but I figure I'd throw that suggestion out. Thanks!
Maybe someday Amarok will support a feature like that. In the meantime, I just created a new application link in KDE and assigned a shortcut key to it. Win+F pops me into full screen mode nicely. Thanks again for your script. It made setting the theme easy for me :-)
Hi could you make a LIRC friendly version of you script.
With klirc you can use dcop of amarok to run your scrip, but you still have to klick on the menu entry to make it appear fullscreen.
It would be cool to just push the button, your script starts an amarokFS will be started push the button once more an amarokFS will be terminated.
Maybe integrade a menu where you can configuer if amarokFS will be startet or not when the script is run.
Thans for this nice script
regards
blubbi
Hmm... nice idea, but I'm not sure that this script is the right place in which to put it. For example, the Fedora version of AmarokFS (the program, not the script) already does something similar to what you want - it starts up/shuts down Amarok for you if it wasn't running already, i.e. you just run "amarokFS" (without running "amarok" first) and it Just Works. :-)
So if you're running Fedora, try binding the "amarokFS" command to klirc instead of just "amarok". If you're not running Fedora, you can download the required patch for this functionality from:
http://cvs.fedora.redhat.com/viewcvs/rpms/amarokFS/devel/?root=extras
(the "amarokFS-0.5-start_amarok.patch" file)
Since AmarokFS itself is now hosted on SourceForge, I will try and merge this patch upstream.
Does this help, or have I misunderstood what you meant?
I added a killall amarokFS to mine to exit using my remote, only downside is i get an error having the program exit unexpectedly
obviously from the killall
X Error: BadDevice, invalid or uninitialized input device 170
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
Major opcode: 149
Minor opcode: 3
Resource id: 0x0
Failed to open device
kwin: unable to claim manager selection, another wm running? (try using --replace)
Terminated
clearly not a clean or good way of doing it but i couldn't think of any other way of stopping it
dcop will let you stop your script but it doesn't kill the application
This script is now available via the Fedora "amarokFS" package.
If you are a Fedora user, type:
yum install amarokFS
to install the AmarokFS application and this script.
I've installed it (i'm on x86_64 fc6)
only a question: what about updating it?
AmarokFS is 0.5 since a week or two...
Now you've updated your script, I hope you could update the rpm package with both the updates (AmrokFs and amarokFs ss)
Thanks a lot for your work.
You just missed it - it was actually submitted to the Fedora buildsystem on the 29th of March. (the script is also in the new package)
By now it should have made its way to your favourite mirror, so just try again. :-)
Hi,
Hmm... didn't notice that script :-).
After some inspection, I can say the following:
- this script handles Amarok crash situations gracefully; it does not have the CPU usage hogging bug that is present in the other script
- this script does not *require* you to specify the location of AmarokFS (as long as it is in your path) (so it's easier/faster to start it for the first time)
- this script allows you to configure it after running (if you want to run a different amarokFS executable, for instance)
- this script handles internal errors gracefully, for instance, it will prompt you again for the amarokFS executable if it gets deleted
So, overally, these two scripts do pretty much the same thing. With all due respect to Kaisermart, I'd say this one is just a bit more polished and robust. :-)
I program the other script but this is better. When amarok crash my script put the cpu load at 100%. I know program in java but no in python. My script is only for learn python. ;)
Ok, version 1.1 of the script uses amarokFS's own "configure" menu, allowing you to configure the theme, among other things.
Thanks Martin Kossler for the patch! :-)
Ratings & Comments
19 Comments
As I know, if users use scim, when they type command in kdialog, it would be like this in config file: ScimInputContextPlugin() QMultiInputContext::changeInputMethod(): index=0, slave=scim ~ScimInputContextPlugin() Maybe in this section, the code: cmd=commands.getoutput('kdialog --inputbox "xxxxxx" 2>/dev/null') would be better. The other some-function script has this problem too,but it is finall version.
First, nice job on this script. It works perfectly. What I would like is either a toolbar button or a shortcut key that would turn on/off your script. Not sure if that is possible but I figure I'd throw that suggestion out. Thanks!
As far as I know, this is sadly not currently possible using an amarok script. :-(
Oh, and thanks! Glad you like the script.
Maybe someday Amarok will support a feature like that. In the meantime, I just created a new application link in KDE and assigned a shortcut key to it. Win+F pops me into full screen mode nicely. Thanks again for your script. It made setting the theme easy for me :-)
Hi could you make a LIRC friendly version of you script. With klirc you can use dcop of amarok to run your scrip, but you still have to klick on the menu entry to make it appear fullscreen. It would be cool to just push the button, your script starts an amarokFS will be started push the button once more an amarokFS will be terminated. Maybe integrade a menu where you can configuer if amarokFS will be startet or not when the script is run. Thans for this nice script regards blubbi
Hmm... nice idea, but I'm not sure that this script is the right place in which to put it. For example, the Fedora version of AmarokFS (the program, not the script) already does something similar to what you want - it starts up/shuts down Amarok for you if it wasn't running already, i.e. you just run "amarokFS" (without running "amarok" first) and it Just Works. :-) So if you're running Fedora, try binding the "amarokFS" command to klirc instead of just "amarok". If you're not running Fedora, you can download the required patch for this functionality from: http://cvs.fedora.redhat.com/viewcvs/rpms/amarokFS/devel/?root=extras (the "amarokFS-0.5-start_amarok.patch" file) Since AmarokFS itself is now hosted on SourceForge, I will try and merge this patch upstream. Does this help, or have I misunderstood what you meant?
I added a killall amarokFS to mine to exit using my remote, only downside is i get an error having the program exit unexpectedly obviously from the killall X Error: BadDevice, invalid or uninitialized input device 170 Major opcode: 149 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 170 Major opcode: 149 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 170 Major opcode: 149 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 170 Major opcode: 149 Minor opcode: 3 Resource id: 0x0 Failed to open device kwin: unable to claim manager selection, another wm running? (try using --replace) Terminated clearly not a clean or good way of doing it but i couldn't think of any other way of stopping it dcop will let you stop your script but it doesn't kill the application
This script is now available via the Fedora "amarokFS" package. If you are a Fedora user, type: yum install amarokFS to install the AmarokFS application and this script.
I've installed it (i'm on x86_64 fc6) only a question: what about updating it? AmarokFS is 0.5 since a week or two... Now you've updated your script, I hope you could update the rpm package with both the updates (AmrokFs and amarokFs ss) Thanks a lot for your work.
You just missed it - it was actually submitted to the Fedora buildsystem on the 29th of March. (the script is also in the new package) By now it should have made its way to your favourite mirror, so just try again. :-)
it work perfectly....thank you very much!
You're welcome! :-)
Hi, does this program anything else than this one?: http://kde-apps.de/content/show.php?content=52787 KapeKa
Hi, Hmm... didn't notice that script :-). After some inspection, I can say the following: - this script handles Amarok crash situations gracefully; it does not have the CPU usage hogging bug that is present in the other script - this script does not *require* you to specify the location of AmarokFS (as long as it is in your path) (so it's easier/faster to start it for the first time) - this script allows you to configure it after running (if you want to run a different amarokFS executable, for instance) - this script handles internal errors gracefully, for instance, it will prompt you again for the amarokFS executable if it gets deleted So, overally, these two scripts do pretty much the same thing. With all due respect to Kaisermart, I'd say this one is just a bit more polished and robust. :-)
I program the other script but this is better. When amarok crash my script put the cpu load at 100%. I know program in java but no in python. My script is only for learn python. ;)
it could be great to add the possibility to manage themes via the startup script instead of launching amarok fs, select theme and re-run the program.
Very good idea! I will look into this.
Ok, version 1.1 of the script uses amarokFS's own "configure" menu, allowing you to configure the theme, among other things. Thanks Martin Kossler for the patch! :-)