|
|
carol.gimp.orgGIMP2 basics guiCustomize Your Splash Screen |
There are several different ways to handle TheGIMP's splash screen; while it is not exactly "Graphical User Interface" it is graphics and it is managed through user interfaces so here it is.
You could always start TheGIMP without the splash screen by typing gimp --no-splash or gimp -s, information easily obtained from the man page or from typing gimp --help into a console:
carol@treva:∼$ gimp --help
GIMP version 2.2.1
Usage: gimp [option ... ] [file ... ]
Options:
-h, --help Output this help.
-v, --version Output version information.
--verbose Show startup messages.
--no-shm Do not use shared memory between GIMP and plugins.
--no-cpu-accel Do not use special CPU accelerations.
-d, --no-data Do not load brushes, gradients, palettes, patterns.
-f, --no-fonts Do not load any fonts.
-i, --no-interface Run without a user interface.
--display <display> Use the designated X display.
-s, --no-splash Do not show the startup window.
--session <name> Use an alternate sessionrc file.
-g, --gimprc <gimprc> Use an alternate gimprc file.
--system-gimprc <gimprc> Use an alternate system gimprc file.
--dump-gimprc Output a gimprc file with default settings.
-c, --console-messages Display warnings to console instead of a dialog box.
--debug-handlers Enable non-fatal debugging signal handlers.
--stack-trace-mode <never | query | always>
Debugging mode for fatal signals.
--pdb-compat-mode <off | on | warn>
Procedural Database compatibility mode.
--batch-interpreter <procedure>
The procedure to process batch commands with.
-b, --batch <commands> Process commands in batch mode.
carol@treva:∼$
|
So many ways to customize Gimp2's splash screens; you used to have to put your own image into the correct place in the sources and recompile it. This is all changed now ....
If you are using the standard gimp install, the following instructions should work. However, if you are using a gimp that you told to use different directories for its resources either when you started it the first time and told it to use different directories than the ones it suggested or by editing this same information via the Preferences Folders dialog, you might need to look back to this to see how to handle this information.
According to the gimp man page in the section with the heading "SPLASH IMAGES" the first place the gimp will look for a splash screen is in a directory created by the user at $HOME/.gimp-2.2/ called splashes. On gnu/linux, this directory can be created by typing mkdir ∼/.gimp-2.2/splashes and the directory can be filled by using "cp" to move your choices of splash images into this directory. If there is more than one image there, the gimp will pick one to use at random.
In this example, the names of all of the images have been prefixed with "splash-", this was done by me to help me keep track of my images. TheGIMP doesn't need this.
carol@treva:∼$ mkdir .gimp-2.2/splashes carol@treva:∼$ cp images/splash-*.png .gimp-2.2/splashes/ carol@treva:∼$ ls .gimp-2.2/splashes splash-concert.png splash-kiss.png splash-pumpkin.png splash-jelly.png splash-lard.png splash-ripramone.png splash-killbill.png splash-previews.png carol@treva:∼$ |
If the gimp fails to find an image in ∼/.gimp-2.2/splashes it will look for an image named "gimp-splash.png" found in each users ∼/.gimp-2.2/ directory.
In this case, the name of the image matters.
carol@treva:∼$ cp images/splash-previews.png .gimp-2.2/gimp-splash.png carol@treva:∼$ |
If you have root access to your computer, you can provide random splashes for all of your users. The method to do this is very similar to the method used by the individual user; the difference being the permission and the location of the resource directory.
As root, make a new directory in /usr/local/share/gimp-2.0/ called splashes. (This how-to assumes a standard build it yourself gimp installation, if you are using a binary provided by a distribution you will need to check with them where they put things.) Then copy the images you wish to randomly display for users who have not done this in their home directory.
In this stage of the TheGIMP's development cycle, the system files are being saved with gimp-2.0 in the prefix while the user directories are being saved with gimp-2.1 or whatever version you are using . This fact is more confounding for people trying to install different versions of gimp2 than it should be for people trying to administrate the resources on their computer. Please do not let it confuse you.
treva:∼# mkdir /usr/local/share/gimp-2.0/splashes
treva:∼# cp /home/carol/images/splash-*.png /usr/local/share/gimp-2.0/splashes/
treva:∼# ls /usr/local/share/gimp-2.0/splashes/
splash-concert.png splash-kiss.png splash-pumpkin.png
splash-jelly.png splash-lard.png splash-ripramone.png
splash-killbill.png splash-previews.png
treva:∼#
|
As root, you can install a single image to be used as the system-wide gimp splash. Similar to the user, it needs to be named gimp-splash.png and needs to be located in TheGIMP's system resource directory.
treva:∼# cp /home/carol/images/splash-previews.png /usr/local/share/gimp-2.0/gimp-splash.png
treva:∼#
|
Failing to find any splashes installed by either the user or the system administrator, TheGIMP will use the splash that was included with the version of gimp that you are using.
I found all of this information in TheGIMP's man page. You can read this and more by typing man gimp at a console prompt.
SPLASH IMAGES
GIMP comes with a default image for the splash screen but it allows
system administrators and users to customize the splash screen by pro-
viding other images. The image to be used with the splash screen is
choosen as follows:
1. GIMP tries to load a random splash screen from the directory
$HOME/.gimp-2.2/splashes.
2. It then falls back to using $HOME/.gimp-2.2/gimp-splash.png.
3. If the user didn?t install any custom splash images, a random
image is picked from ${prefix}/share/gimp-2.0/splashes.
4. As a last resort, GIMP uses the default splash image located at
${prefix}/share/gimp/2.0/images/gimp-splash.png.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
