
KSplasher - KDE Moodin Splash Screen Edi
Source (link to git-repo or to original if based on someone elses unmodified work):
---------
KDE Moodin Engine Splash Screen Editor and Creator
Create your own Splash Screens or edit existing ones.
Made with python+pygame. GUI by PGU. Needs PIL for PNG saving.
The KSplasher logo created by Divilinux.
v0.9.8: - You can load a tar compressed theme file and modify. (.tar, .tar.gz, .tar.bz2, etc)
- You can create a .tar.gz file, and then imports it with your kcontrol and test it.
- Fixed coding of resulting theme.rc file now works with kcontrol!
- You can now create preview.png file (automated when saving as .tar.gz), but this needs an additional module named "PIL" or "python-imaging".
v0.9.1: Now you can change author info.
Don't forget to "save theme.rc file" after make your changes.
-- Fixed start bug (CAPS problem in void background). Now works well. --
v0.9: A big jump. KSplasher has a GUI. You can load a theme folder from anywhere. You don't need to close the program to load a new source.
v0.11: Few minor bugfixes. You don't need NUMPY anymore. Just Python and Pygame. Added a Quick Readme file.
v0.1: Program functional. Released as alpha.
Ratings & Comments
10 Comments
This may sound like a real dumb question, but I'm not that sure... Where should I place the file once I have extracted it? To be able to use it, that is... I have always revamped splashes vis editing the theme.rc, and this looks like a much easier way. Do I understand correctly, it looks as though I would be able to drag the items (.pngs etc) to where I want with my mouse? Any help is appreciated Thanks
At the time, the program is standalone, so you must extract it wherever you want (example, your "~" directory), and run it with console "python ksplasher.py". Don't forget to install packages python, python-pygame, python-imaging or you will have errors. The ideal use for this program is to load the compressed file directly, edit it, and then save as .tar.gz (this allows you to load it directly to kcontrol for testing). The new file will be saved in the ksplasher main directory with the name of your theme as name of your .tar.gz file. Hope this helps. By the way, i'm not dead, i'm working porting this app to pyqt4 (so i'm rewritting it) for better compatibility with KDE 3/4. See ya.
Hello, I would like to test your ksplasher, but I'm missing some standard way of setup. Could you provide setup.py? Cheers, Jiri
Thnx for asking. Yes, the next release will have some kind of setup. (this is a one-man project, and i've been working in complete basic features). But yes, it will be. By the way... where do you think that KSPlasher suppose to be located (which path, which kmenu, etc..)??? Regards, XaniloM.
It should use kde-config to get the KDE prefix and then use the standard path for everything else.
OK, Ksplasher is now fully functional, we have just a few small TODO, so feedback is needed for enhancing it. Regards, XaniloM
Hi A friend of mine has realized a new fresh logo for your good app. I give you the link..send me feedback ;) regards http://www.mediafire.com/?km97joxyo1j
Thanks a lot! It is clear that the design is not my strongest quality. Thnx for helping the Free World to work as it could be (sharing work is the key). I'm planning to use your logo for the next release of KSplasher, assuming that is licensed as Artistic, or GPL, or whatever that allows me to use it. If you wants to participate a little more i'm also requesting an icon for KSplasher. greetings from the world's end.
I think it's very great!Can I ask you a question?Is there something like this also for grub gfxboot themes?
Thnx! Well, by now, i'm working in a GUI for KSplasher, that allows user more control about the changes on the fly. Also, i'm implementig the ability to load the themes directly from the .tar.gz archive. After that i'm planning to create a KDM login screen editor, which is in the practice about the same than KSplasher, but with XML generation beside TXT. I haven't tried gfxboot so i can't figure if KSplasher can be transformed to work with gfxboot, but if it can, it will be implemented later.