Log in or Sign up
Coin Talk
Home
Forums
>
Coin Forums
>
Coin Chat
>
New camera shots.
>
Reply to Thread
Message:
<p>[QUOTE="mrbrklyn, post: 463799, member: 4381"]You are probably using Windows or some GNU/Linux window manager that does not support the "Utility window" hint. Right now you can use list of currently opened images in "Windows" menu.</p><p><br /></p><p>If you are using GNU/Linux or some free UNIX-like system and not willing to use GNOME and Metacity (its window manager) which does support "Utility window" hint, alternatively you can use a window manager like Fluxbox where you can apply this "always on top" property to the toolbox and layers dialogue. Window managers like Fluxbox also allow you to focus, or even raise, a window whenever you move the mouse over it (usually you have to click on a window before it will focus). Fluxbox allows you to stack windows together and the tab between them, much like Firefox can tab between web pages. Combined with focus-follows-mouse, this may increase one's workflow considerably. Fluxbox also requires very few resources meaning more memory for your images. Finally, don't forget about keyboard shortcuts and modifiers. Learning these means you rarely have to visit the toolbox.</p><p><br /></p><p>In the mean time, during 2.7.x development cycle we will do our best to switch to tabbed user interface with docked palettes.</p><p>Is there a macro recording interface?</p><p><br /></p><p>Not at this time. With GIMP based on GEGL, so that all changes are non-destructive, it will be much easier to implement this feature by just remembering all nodes in given range and reapplying them to other images. This is something that can be part of a future release of GIMP like 3.0.</p><p>How do I configure my X server to do global gamma correction?</p><p><br /></p><p>Some servers have no facility for this; you may be able to adjust your monitor to correct somewhat. Later versions of XFree86 allow these server options:</p><p><br /></p><p> *</p><p><br /></p><p> -gamma f set gamma value (0.1 < f < 10.0) Default: 1.0 -rgamma f set gamma value for red phase -ggamma f set gamma value for green phase -bgamma f set gamma value for blue phase</p><p><br /></p><p>How do I fill with transparent?</p><p><br /></p><p>If your image doesn't have an alpha channel, add one with Layers->Add Alpha Channel. Select the area you want to clear (if not the whole image). To change everything of a particular color transparent, pick Select->By Color... and click on the color in the image you want to replace. Then select Edit->Clear. That's it.</p><p><br /></p><p>Any dithering, blurring, or related effects against the color you replace will be against the original color. This usually requires you to do some form of cleanup of the edge pixels. In cases likely to result in this, change the color to transparent as early as reasonably possible to preclude extra "cleanup" work.</p><p>How do I draw in a different color?</p><p><br /></p><p>At the bottom of the toolbar there is a box with two smaller boxes and an arrow. The uppermost box displays the current foreground color; the lowermost box displays the current background color. You can single-click on the arrow to switch these two. You can also double-click on either of the color boxes (or single-click if that box is already selected) to pop up a color selection tool, with which you can elect any color you like for that box. That color then becomes the new foreground or background color. Subsequent drawing operations (including text and color fill) will now use these colors.</p><p>How can I export my path to SVG?</p><p><br /></p><p>Open the dialog "paths", right click the path you want to export, click "Export path..." and save it as "yourpath.svg".</p><p>How do I do something really simple like blur?</p><p><br /></p><p>There are two methods, one for the current selection or current layer and one tool to blur using mouse. The tool looks like a waterdrop. Click it (or use shortcut V) and hold down the left mouse button while moving the mouse cursor over the desired area. Method two uses the blur filter (Filters -> Blur filters -> Blur) and as said it applies to the current selection and/or layer.</p><p>I've tried to use GIMP but I just don't get it - what am I missing (and I know nothing about images so dont start about alpha channels and layers, etc).</p><p><br /></p><p>There is plenty of documentation. See <a href="http://docs.gimp.org/en/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://docs.gimp.org/en/" rel="nofollow">http://docs.gimp.org/en/</a> If you need a complete course about photoediting, image manipulation etc. then a book would be the best to start with.</p><p>Example books:</p><p>"Beginning GIMP: From Novice to Professional" - Akkana Peck</p><p>"GIMP Pocket Reference" - Sven Neumann</p><p>"Gimp: The Official Handbook" - Karin Kylander, Olof S. Kylander</p><p>"GIMP Visual Quickstart Guide" - Phyllis Davis</p><p>"Guerrilla Guide to Great Graphics With the Gimp" - David D. Busch</p><p>and many many more! Check your local books-dealer!</p><p>How can I paint easily an (OutLined) rectangle using GIMP?</p><p><br /></p><p>Use "Rectangle Select" tool (see <a href="http://docs.gimp.org/en/gimp-tools-selection.html" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://docs.gimp.org/en/gimp-tools-selection.html" rel="nofollow">http://docs.gimp.org/en/gimp-tools-selection.html</a>) for making a selection in the form of a rectangle. Then use "Edit" -> "Stroke Selection" (see <a href="http://docs.gimp.org/en/gimp-selection-stroke.html" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://docs.gimp.org/en/gimp-selection-stroke.html" rel="nofollow">http://docs.gimp.org/en/gimp-selection-stroke.html</a>). The "Rectangle Select" tool has the shortcut "R".</p><p>How do I edit properties of existing guides? How do I move existing guides?</p><p><br /></p><p>Use the Move tool (Toolbox) or press M, then click and drag a guide. If the dragging moves the layer you have to switch modes (hold the shift-key while dragging or click "Pick a layer or guide" in the Move Tool options window). See "Grids and Guides" section of the online manual at <a href="http://docs.gimp.org/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://docs.gimp.org/" rel="nofollow">http://docs.gimp.org/</a></p><p>How do I select the layer currently shown under the mouse cursor? Is there a shortcut?</p><p><br /></p><p>There isn't a context menu or shortcut. But you can move visible layers (not overlapped by another one) with the move tool (and holding down the shift key). Use the Move tool (Toolbox) or press M, then click and move a layer. If the dragging moves the currently selected layer you have to switch modes (hold the shift-key while dragging or click "Pick a layer or guide" in the Move Tool options window). This doesn't select the layer, it only moves it. See "Move tool" section of the online manual at <a href="http://docs.gimp.org/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://docs.gimp.org/" rel="nofollow">http://docs.gimp.org/</a></p><p>How can you wrap text using the Font tool? There are alignment buttons (including justified) but they have little effect since I can't work out how to make the text wrap.</p><p><br /></p><p>Text cannot be wrapped automatically. But when you type some text in the text-editing dialog you can just hit enter for a new line. In that case the alignment buttons would apply.</p><p>Why do I have to make my rectangular selection exactly right the first time? Why can't I move and resize a rectangular selection using handles?</p><p><br /></p><p>You can, at least in version 2.3.10 of GIMP. (notice the small arrows at each edge of the rectangular selection.)</p><p>I recently saw a project that specified files were to be saved in Photoshop "Save for Web -> High (15K to 30K Optimized)" format. Is there an equivalent in GIMP?</p><p><br /></p><p>Yes, there is a plug-in for GIMP which is called "Save for Web" and created by Aurimas Juška as a Google Summer of Code SOC project. It allows visual adjustment of various image parameters such as quality, number of colors, dimensions, etc to reach optimal file size.", see <a href="http://registry.gimp.org/node/33" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://registry.gimp.org/node/33" rel="nofollow">http://registry.gimp.org/node/33</a>.</p><p>How do I get GIMP to be by default image tool i.e. I installed another program & it is now associated to auto-opening them.</p><p><br /></p><p>It depends on what operating system you are using.</p><p><br /></p><p> *</p><p><br /></p><p> Windows: Right-click on an image in explorer and select "Open with..." in the context menu. Select GIMP and mark "Use this program as standard for openening this filetype". Now the filetype of that image should be properly associated with GIMP.</p><p> *</p><p><br /></p><p> GNU/Linux (KDE): Right-click on an image in konqueror, select "Open with..." -> "Other" in the context menu, select GIMP and check the box "Associate filetype with this program".</p><p> *</p><p><br /></p><p> For all other operating systems check the manual of the os.</p><p><br /></p><p>Common Feature Requests</p><p>When can we see layer groups?</p><p><br /></p><p>Sometimes it is nice to place layers in groups. It makes them easier to organise when you have lots of them. It also means you can easily apply the same effect to lots of layers, without directly affecting those layers. Long story short, it makes life easier. This will be much easier to program once GEGL has been integrated into GIMP.</p><p>When can we see 16-bit per channel support (or better)?</p><p><br /></p><p>For some industries, especially photography, 24-bit colour depths (8 bits per channel) are a real barrier to entry. Once again, it's GEGL to the rescue. Work on integrating GEGL into GIMP will begin after 2.4 is released. Once that work is completed, GIMP will support 16 bits per channel. If you need such support now and can't wait, cinepaint and krita support 16 bits per channel now.</p><p><br /></p><p>It should be noted that for publishing to the web, the current GIMP release is good enough.</p><p>When will an MDI/nested windows be implemented?</p><p><br /></p><p>This is often requested by MS Windows users who lack some of the window management features common in other operating systems. An MDI interface is largely considered a step backwards by interface designers. The core GIMP developers share this sentiment, so don't expect them to implement the feature any time soon. However, there are no objections to the feature itself. So far only the Deweirifyer plugin attempts any sort of a fix. It seems to be good enough for some, but not for others. If you are interested in implementing MDI support bug 7379 is the place to start.</p><p>How should I make feature requests?</p><p><br /></p><p>The first thing to do is see if your request has already been made. It probably has; we get a lot of feature requests. Check the user and developer mailing-list archives and search bugzilla. If you find a discussion that seems relevant, feel free to add your two penneth.</p><p><br /></p><p>If you are making a new feature request, please make it to the gimp-user or -developer mailing list first and not bugzilla. Think about what it is you are trying to achieve with your request and not about what the underlying procedure is. We get a lot of requests from Photoshop users who simply ask for their favourite Photoshop tool without saying what it does and why it is useful to them. Once we understand what the tool is for, we may find that we can do it better, or that the way it works in Photoshop isn't suitable for GIMP's interface, or that GIMP already supports the feature, but in a different way.</p><p><br /></p><p>Once the feature has been discussed on the mailing list, a bug report should be opened so that record can be kept on its progress.</p><p><br /></p><p>Sven Neumann has this to say on the matter of a "polygon select" feature requests:</p><p><br /></p><p> *</p><p><br /></p><p> No tool should be written without doing a full specification beforehand and discussing this spec on the mailing-list(s). Bugzilla is the wrong place for such a discussion. If you want to do something to help, please make a list of usage scenarios that involve creating polygonal selections. Then analyze how these scenarios can be performed using the existing tools and identify problems.</p><p><br /></p><p> With the list of scenarios and problems, you are then able to analyze and to compare different possible solutions. These solutions might involve changing existing tools or adding new one(s). As soon as we have identified the best solution, it can be fully specified. Only then can someone can start to implement it.</p><p><br /></p><p>Plug-Ins</p><p>What are plug-ins?</p><p><br /></p><p>Plug-ins are external modules that actually do the nifty graphics transformations. There is a plug-in registry at <a href="http://registry.gimp.org/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://registry.gimp.org/" rel="nofollow">http://registry.gimp.org/</a> with the latest plug-ins, maintained by Ingo Lütkebohle. [Special thanks to Adam Moss for the original registry!]</p><p>How do I add new plug-ins?</p><p><br /></p><p>First, copy the plug-in<strike> to your plug-in directory (typically /usr/local/lib/gimp/$VERSION/plug-ins/).</strike></p><p><strike><br /></strike></p><p><strike>After copying the plug-in to its proper directory, just run GIMP. It should automatically find new plug-ins.</strike></p><p><strike>How do I build new plug-ins?</strike></p><p><strike><br /></strike></p><p><strike>You'll need a copy of the source directories. Build GIMP. Place the new plug-in in the plug-ins directory. The docs with the new plug-in hopefully identify any special libraries it needs. Look for a plug-in with similar libraries (if all else fails, look at xpm and whirlpinch).</strike></p><p><strike><br /></strike></p><p><strike>With newer versions, if the plug-in is contained in a single source file, you should just have to run gimptool in the plug-in's directory :</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> gimptool --build plugin.c</strike></p><p><strike><br /></strike></p><p><strike>For older versions, there are several methods. The first two walk you through a number of steps manually; these are the most thorough, but also require more work on your part. The last ones are scripts of one sort or another, and are easier on your part -- if they work with your system. Go ahead and try - you can always fall back on the first methods.</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> The best way to procede is to edit the Makefile. Pick a similar plug-in (such as whirlpinch). For the SRC and OBJ lines, just add entries similar to the others, but with the new plug-in's name. Now, find all the groups of lines with the other plug-in's name in them, duplicate them, and change the old name to the new name. The one exception is the huge set of lines that have a lot of paths that end in .h - do not bother with these. Now, just type</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> make</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> and it should build. Install it wherever your other plug-ins are installed.</strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> A second choice for those who don't want to mess with the main Makefile is to build a file to create just the new plug-in. Start the same way - pick a similar plug-in. Now remove the binary and object files for the one you just picked. For instance, if you selected the whirlpinch plug-in, you will see the following files:</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> whirlpinch whirlpinch.c whirlpinch.o</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> In this case, you would remove the first and last files, leaving the whirlpinch.c file. Now type</strike></p><p><strike><br /></strike></p><p><strike> make</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> to rebuild the old plug-in.</strike></p><p><strike><br /></strike></p><p><strike> Copy the output (cut and paste it!) into a file. Edit the file and change all occurances of "whirlpinch" (or whatever) to the name of the new plug-in. Execute the file you just edited. For instance, if the file is make_plug-in, just type</strike></p><p><strike><br /></strike></p><p><strike> make_plugin</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> and it should work. The copy the plug-in to wherever the others are installed on your system.</strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> A Makefile</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> First, load Makefile-pi provided by Ciccio C. Simon . Change all occurances of the word sharpen in Makefile-pi to the name of the new plug-in. Then type</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> make -f Makefile-pi</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> and watch it (hopefully) work.</strike></p><p><strike><br /></strike></p><p><strike> If it doesn't work, try the next method.</strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> A compile script</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> First, load the compile-pi script provided by Jeremy Dinsel . Change the permissions on compile-pi as follows:</strike></p><p><strike> o</strike></p><p><strike><br /></strike></p><p><strike> chmod ugo+rx compile-pi</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> and type</strike></p><p><strike><br /></strike></p><p><strike> compile-pi help</strike></p><p><strike> +</strike></p><p><strike><br /></strike></p><p><strike> for instructions. Follow those instructionms. If this one also fails, go back to the earlier, manual methods; you have too picky a configuration for the simple methods to work.</strike></p><p><strike><br /></strike></p><p><strike>If you need more help, ask your system administrator or a handy programmer, or get a good book on make (such as O'Reilly's). You may want to join the GIMP developer's list as well (see the Developer FAQ).</strike></p><p><strike>Is there a plug-in for ... ?</strike></p><p><strike><br /></strike></p><p><strike>The plug-in registry referenced above is the place to check.</strike></p><p><strike>Why did some plug-ins disappear for 0.99.19?</strike></p><p><strike><br /></strike></p><p><strike>Some of the plug-ins have proven unstable. These have been moved into a separate download, which should be available wherever you got the GIMP, in the file gimp-plugins-unstable-VERSION.tar.gz or gimp-plugins-unstable-VERSION.tar.bz2 .</strike></p><p><strike><br /></strike></p><p><strike>Since this list may change frequently, the unstable plug-ins are no longer listed here. Script-Fu</strike></p><p><strike>What is Script-Fu?</strike></p><p><strike><br /></strike></p><p><strike>In the words of S&P:</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> Script-Fu is the first GIMP scripting extension. Extensions are separate processes that communicate with the GIMP in the same way that plug-ins do. The distinction is that extensions don't require an active image to operate on, instead extending GIMP's functionality. GIMP internals for version 1.0 have been completely overhauled from version 0.54. In particular, the plug-in API has been made far more general with the advent of the procedural database (PDB). The PDB allows GIMP and its plug-ins to register procedures which can then be called from anywhere: internally, from extensions, and from plug-ins. There are already over 200 internal GIMP procedures, and more being created all the time. Because all of these procedures can be easily invoked from extensions, the logical next step was to create a scripting facility; thus, Script-Fu was born.</strike></p><p><strike><br /></strike></p><p><strike>Where can I learn about Script-Fu?</strike></p><p><strike><br /></strike></p><p><strike>As with plug-ins, web pages, COBOL, or anything else, one of the best things you can do is look at other peoples' code, and play with it. But it helps a lot if you know Scheme.</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> = S&P's Script-Fu pages at <a href="http://www.xcf.berkeley.edu/~gimp/script-fu/script-fu.html" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://www.xcf.berkeley.edu/~gimp/script-fu/script-fu.html" rel="nofollow">http://www.xcf.berkeley.edu/~gimp/script-fu/script-fu.html</a> = Mike Terry's Black Belt School of Script-Fu at <a href="http://manual.gimp.org/manual/GUM/write_scriptfu3.html" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://manual.gimp.org/manual/GUM/write_scriptfu3.html" rel="nofollow">http://manual.gimp.org/manual/GUM/write_scriptfu3.html</a></strike></p><p><strike><br /></strike></p><p><strike>How do I call one script-fu script from another?</strike></p><p><strike><br /></strike></p><p><strike>The trick to calling script-fu-scripts from another script is to just reference the main define for the script and not to try to use the pdb call. All the scripts in script-fu share a common name space; you call other scripts just like a regular function / define / whatever you call those those things in_scheme.</strike></p><p><strike><br /></strike></p><p><strike>Ie, to call script-fu-predator in a script, just use</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> (script-fu-predator img drawable 2 TRUE 3 TRUE TRUE)</strike></p><p><strike><br /></strike></p><p><strike>For examples, see</strike></p><p><strike><br /></strike></p><p><strike> *</strike></p><p><strike><br /></strike></p><p><strike> <a href="http://adrian.gimp.org/scripts/test.scm" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://adrian.gimp.org/scripts/test.scm" rel="nofollow">http://adrian.gimp.org/scripts/test.scm</a> .</strike></p><p><strike><br /></strike></p><p><strike>How do I call a plug-in from script-fu?</strike></p><p><strike><br /></strike></p><p><strike>The following examples assume the plug-in name is "plug_in_randomize_hurl", and the plug-in has four parameters specific to it, the first two of which are floats, and the next two ints.</strike></p><p><strike><br /></strike></p><p><strike>From the script-fu console, call a plug-in like this:</strike></p><p><strike><br /></strike></p><p><strike>(plug-in-name 1 0 0 100.0 1.0 10 0) </strike></p><p><strike><br /></strike></p><p><strike>The first parameter should always be a "1". The next two are the image number and drawable. Anything following these numbers will be plug-in parameters, which depend on the plug-in.</strike></p><p><strike><br /></strike></p><p><strike>Inside an actual script, call a plug-in like this:</strike></p><p><strike><br /></strike></p><p><strike> (define (script-fu-fred img drawable)</strike></p><p><strike><br /></strike></p><p><strike> (plug-in-randomize-hurl 1 img drawable 100.0 1.0 10 0)</strike></p><p><strike> (gimp-displays-flush)</strike></p><p><strike><br /></strike></p><p><strike> )</strike></p><p><strike><br /></strike></p><p><strike> (script-fu-register "script-fu-fred" "<Image>/Script-Fu/fred"</strike></p><p><strike> "Randomize test" "Miles O'Neal <meo@rru.com>" "Miles O'Neal"</strike></p><p><strike> "1998/May/1" "RGB*, GRAY*, INDEXED*" SF-IMAGE "Image" 0 SF-DRAWABLE</strike></p><p><strike> "Drawable" 0) </strike></p><p><strike><br /></strike></p><p><strike>How do I execute script-fu from batch mode?</strike></p><p><strike><br /></strike></p><p><strike>Invoke the script as non-interactive and add a pair of escaped quotes around each string just like you do in (script-fu-register). You DO NOT need to replace '-' with '_' in any names or registrations.</strike></p><p><strike><br /></strike></p><p><strike>Example script:</strike></p><p><strike><br /></strike></p><p><strike> (define (script-fu-famhist-link text filename) ;; code ommitted</strike></p><p><strike>for brevity (file-gif-save 1 img 0 filename "" FALSE FALSE 0 0))</strike></p><p><strike><br /></strike></p><p><strike>(script-fu-register "script-fu-famhist-link"</strike></p><p><strike>"<Toolbox>/Xtns/Script-Fu/Family Historian/Link" "Family Historian</strike></p><p><strike>Link" "John Johnson" "John Johnson" "1998" "" SF-VALUE "Text String"</strike></p><p><strike>"\"Family Historian\"" SF-VALUE "Base filename" "\"foo\"")</strike></p><p><strike><br /></strike></p><p><strike>Example Invocation:</strike></p><p><strike><br /></strike></p><p><strike>;; note the '1' as the first argument tell it to run non-interactivly ;;</strike></p><p><strike>note the \" \" pairs around the strings</strike></p><p><strike><br /></strike></p><p><strike>gimp -n -b '(script-fu-famhist-link 1 "\"Introduction\"" \</strike></p><p><strike>"\"intro.gif\"")' '(gimp-quit 0)' </strike></p><p><strike><br /></strike></p><p><strike>For a detailed, step by step explanation, check out Adrian's GIMP Batch Mode how-to at <a href="http://adrian.gimp.org/batch/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://adrian.gimp.org/batch/" rel="nofollow">http://adrian.gimp.org/batch/</a> .</strike></p><p><strike>What does ``procedural-database-error'' in script-fu mean?</strike></p><p><strike><br /></strike></p><p><strike>Normally it means that the script is trying to use a particular font that isn't available on your system - it's either not installed or not in your X server's FONTPATH. The base script-fu package makes extensive use of the freefont package, and at least one font (AlfredDrake) from the sharefont package.</strike></p><p><strike>What is Net-Fu? Where is it?</strike></p><p><strike><br /></strike></p><p><strike>Net-fu is a web-based interface to a script-fu server. The work is done at a remote site. To see Net-fu, point your web browser at <a href="http://ftp://ftp.gimp.org/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://ftp://ftp.gimp.org/" rel="nofollow">ftp://ftp.gimp.org/</a> or one of the miiror sites, and then go to "gimp/net-fu/". Any web browser can read net-fu pages; the browser must be Java-enabled to actually run Script-fu. Fonts</strike></p><p><strike>Where can I get the fonts I'm missing?</strike></p><p><strike><br /></strike></p><p><strike>The freefonts and sharefonts packages are both available from <a href="http://ftp://ftp.funet.fi/pub/Linux/mirrors/metalab/X11/fonts/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://ftp://ftp.funet.fi/pub/Linux/mirrors/metalab/X11/fonts/" rel="nofollow">ftp://ftp.funet.fi/pub/Linux/mirrors/metalab/X11/fonts/</a> or other metalab mirrors. If you get the sharefonts package, be sure and read the various licensing agreements, and abide by them.</strike></p><p><strike>How can I change the GIMP font?</strike></p><p><strike><br /></strike></p><p><strike>You need to copy the gtkrc file that comes with the GIMP source (in the top level directory) into $HOME/.gimp/gtkrc . As of 0.99.10, this should be recognized. You then go in and edit the default font style, the one that looks like this:</strike></p><p><strike><br /></strike></p><p><strike> style "default" { font =</strike></p><p><strike>"-adobe-helvetica-medium-r-normal--*-100-*-*-*-*-*-*" } </strike></p><p><strike><br /></strike></p><p><strike>I'm sure ther's a lot of clever stuff that can be done here, and I'll try to track it down soon, but in the meantime, just change that "100" to something larger, like "120" or "140". (The number is points= 10, so 100 is a 10 point font).</strike></p><p><strike><br /></strike></p><p><strike>Obviously, you could stick in any font you have available.</strike></p><p><strike>Why don't the Far Eastern fonts work?</strike></p><p><strike><br /></strike></p><p><strike>These are 16 bit fonts, with thouousands and thouousands of characters. And the characters are more complex, which means (usually) more bits per character, which means more memory and more processing time.</strike></p><p><strike><br /></strike></p><p><strike>This includes fonts such as kana, kanji, song ti, mincho and gothic. (If you look carefully at the fully qualified font name for gothic via xfontsel, you'll see clues. It's a daewoo font. The gothic name is misleading to western minds, but no doubt means something to its author<strike>.)</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>Check one of these out in a program that shows a font as pages (such as xfd).. You can keep hitting next page to see a new page of characters, almost forever.</strike></strike></p><p><strike><strike>What about TrueType fonts?</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>If neither your X server nor your X font server supports you can try one of the TruType font servers: xfstt (<a href="http://sunsite.unc.edu/pub/Linux/X11/fonts/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://sunsite.unc.edu/pub/Linux/X11/fonts/" rel="nofollow">http://sunsite.unc.edu/pub/Linux/X11/fonts/</a>) or xfsft (<a href="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/" target="_blank" class="externalLink ProxyLink" data-proxy-href="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/" rel="nofollow">http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/</a> .</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>xfstt supposedly has limitations on the font size. File Formats</strike></strike></p><p><strike><strike>What is GIMP's native graphics file format?</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>XCF is GIMP's "native" format. This will preserve all information about an image, including the layers.</strike></strike></p><p><strike><strike>What other graphics file types are supported?</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>All the common formats, and many more as well, including GIF, TIFF, JPEG, XBM, XPM, PostScript, and BMP. Plug-ins are used to load and save files so adding new file types is very simple, compared to other graphics programs.</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>As of July 1, 1998, the list of supported types included BMP, CEL, FITS, FLI, GBR, Gicon, GIF, GIcon, HRZ, JPEG, PAT, PCX, PIX, PNG, PNM, PostScript, SGI, Sun Raster, TGA, TIFF, XPM, XWD and XCF. Bzipped, Gzipped and Xdelta'd files are understood, and URL support is provided.</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike>Of course, plug-ins for other types may be available at the plug-in registry .</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike> *</strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike><br /></strike></strike></p><p><strike><strike> *</strike></strike>[/QUOTE]</p><p><br /></p>
[QUOTE="mrbrklyn, post: 463799, member: 4381"]You are probably using Windows or some GNU/Linux window manager that does not support the "Utility window" hint. Right now you can use list of currently opened images in "Windows" menu. If you are using GNU/Linux or some free UNIX-like system and not willing to use GNOME and Metacity (its window manager) which does support "Utility window" hint, alternatively you can use a window manager like Fluxbox where you can apply this "always on top" property to the toolbox and layers dialogue. Window managers like Fluxbox also allow you to focus, or even raise, a window whenever you move the mouse over it (usually you have to click on a window before it will focus). Fluxbox allows you to stack windows together and the tab between them, much like Firefox can tab between web pages. Combined with focus-follows-mouse, this may increase one's workflow considerably. Fluxbox also requires very few resources meaning more memory for your images. Finally, don't forget about keyboard shortcuts and modifiers. Learning these means you rarely have to visit the toolbox. In the mean time, during 2.7.x development cycle we will do our best to switch to tabbed user interface with docked palettes. Is there a macro recording interface? Not at this time. With GIMP based on GEGL, so that all changes are non-destructive, it will be much easier to implement this feature by just remembering all nodes in given range and reapplying them to other images. This is something that can be part of a future release of GIMP like 3.0. How do I configure my X server to do global gamma correction? Some servers have no facility for this; you may be able to adjust your monitor to correct somewhat. Later versions of XFree86 allow these server options: * -gamma f set gamma value (0.1 < f < 10.0) Default: 1.0 -rgamma f set gamma value for red phase -ggamma f set gamma value for green phase -bgamma f set gamma value for blue phase How do I fill with transparent? If your image doesn't have an alpha channel, add one with Layers->Add Alpha Channel. Select the area you want to clear (if not the whole image). To change everything of a particular color transparent, pick Select->By Color... and click on the color in the image you want to replace. Then select Edit->Clear. That's it. Any dithering, blurring, or related effects against the color you replace will be against the original color. This usually requires you to do some form of cleanup of the edge pixels. In cases likely to result in this, change the color to transparent as early as reasonably possible to preclude extra "cleanup" work. How do I draw in a different color? At the bottom of the toolbar there is a box with two smaller boxes and an arrow. The uppermost box displays the current foreground color; the lowermost box displays the current background color. You can single-click on the arrow to switch these two. You can also double-click on either of the color boxes (or single-click if that box is already selected) to pop up a color selection tool, with which you can elect any color you like for that box. That color then becomes the new foreground or background color. Subsequent drawing operations (including text and color fill) will now use these colors. How can I export my path to SVG? Open the dialog "paths", right click the path you want to export, click "Export path..." and save it as "yourpath.svg". How do I do something really simple like blur? There are two methods, one for the current selection or current layer and one tool to blur using mouse. The tool looks like a waterdrop. Click it (or use shortcut V) and hold down the left mouse button while moving the mouse cursor over the desired area. Method two uses the blur filter (Filters -> Blur filters -> Blur) and as said it applies to the current selection and/or layer. I've tried to use GIMP but I just don't get it - what am I missing (and I know nothing about images so dont start about alpha channels and layers, etc). There is plenty of documentation. See [url]http://docs.gimp.org/en/[/url] If you need a complete course about photoediting, image manipulation etc. then a book would be the best to start with. Example books: "Beginning GIMP: From Novice to Professional" - Akkana Peck "GIMP Pocket Reference" - Sven Neumann "Gimp: The Official Handbook" - Karin Kylander, Olof S. Kylander "GIMP Visual Quickstart Guide" - Phyllis Davis "Guerrilla Guide to Great Graphics With the Gimp" - David D. Busch and many many more! Check your local books-dealer! How can I paint easily an (OutLined) rectangle using GIMP? Use "Rectangle Select" tool (see [url]http://docs.gimp.org/en/gimp-tools-selection.html[/url]) for making a selection in the form of a rectangle. Then use "Edit" -> "Stroke Selection" (see [url]http://docs.gimp.org/en/gimp-selection-stroke.html[/url]). The "Rectangle Select" tool has the shortcut "R". How do I edit properties of existing guides? How do I move existing guides? Use the Move tool (Toolbox) or press M, then click and drag a guide. If the dragging moves the layer you have to switch modes (hold the shift-key while dragging or click "Pick a layer or guide" in the Move Tool options window). See "Grids and Guides" section of the online manual at [url]http://docs.gimp.org/[/url] How do I select the layer currently shown under the mouse cursor? Is there a shortcut? There isn't a context menu or shortcut. But you can move visible layers (not overlapped by another one) with the move tool (and holding down the shift key). Use the Move tool (Toolbox) or press M, then click and move a layer. If the dragging moves the currently selected layer you have to switch modes (hold the shift-key while dragging or click "Pick a layer or guide" in the Move Tool options window). This doesn't select the layer, it only moves it. See "Move tool" section of the online manual at [url]http://docs.gimp.org/[/url] How can you wrap text using the Font tool? There are alignment buttons (including justified) but they have little effect since I can't work out how to make the text wrap. Text cannot be wrapped automatically. But when you type some text in the text-editing dialog you can just hit enter for a new line. In that case the alignment buttons would apply. Why do I have to make my rectangular selection exactly right the first time? Why can't I move and resize a rectangular selection using handles? You can, at least in version 2.3.10 of GIMP. (notice the small arrows at each edge of the rectangular selection.) I recently saw a project that specified files were to be saved in Photoshop "Save for Web -> High (15K to 30K Optimized)" format. Is there an equivalent in GIMP? Yes, there is a plug-in for GIMP which is called "Save for Web" and created by Aurimas Juška as a Google Summer of Code SOC project. It allows visual adjustment of various image parameters such as quality, number of colors, dimensions, etc to reach optimal file size.", see [url]http://registry.gimp.org/node/33[/url]. How do I get GIMP to be by default image tool i.e. I installed another program & it is now associated to auto-opening them. It depends on what operating system you are using. * Windows: Right-click on an image in explorer and select "Open with..." in the context menu. Select GIMP and mark "Use this program as standard for openening this filetype". Now the filetype of that image should be properly associated with GIMP. * GNU/Linux (KDE): Right-click on an image in konqueror, select "Open with..." -> "Other" in the context menu, select GIMP and check the box "Associate filetype with this program". * For all other operating systems check the manual of the os. Common Feature Requests When can we see layer groups? Sometimes it is nice to place layers in groups. It makes them easier to organise when you have lots of them. It also means you can easily apply the same effect to lots of layers, without directly affecting those layers. Long story short, it makes life easier. This will be much easier to program once GEGL has been integrated into GIMP. When can we see 16-bit per channel support (or better)? For some industries, especially photography, 24-bit colour depths (8 bits per channel) are a real barrier to entry. Once again, it's GEGL to the rescue. Work on integrating GEGL into GIMP will begin after 2.4 is released. Once that work is completed, GIMP will support 16 bits per channel. If you need such support now and can't wait, cinepaint and krita support 16 bits per channel now. It should be noted that for publishing to the web, the current GIMP release is good enough. When will an MDI/nested windows be implemented? This is often requested by MS Windows users who lack some of the window management features common in other operating systems. An MDI interface is largely considered a step backwards by interface designers. The core GIMP developers share this sentiment, so don't expect them to implement the feature any time soon. However, there are no objections to the feature itself. So far only the Deweirifyer plugin attempts any sort of a fix. It seems to be good enough for some, but not for others. If you are interested in implementing MDI support bug 7379 is the place to start. How should I make feature requests? The first thing to do is see if your request has already been made. It probably has; we get a lot of feature requests. Check the user and developer mailing-list archives and search bugzilla. If you find a discussion that seems relevant, feel free to add your two penneth. If you are making a new feature request, please make it to the gimp-user or -developer mailing list first and not bugzilla. Think about what it is you are trying to achieve with your request and not about what the underlying procedure is. We get a lot of requests from Photoshop users who simply ask for their favourite Photoshop tool without saying what it does and why it is useful to them. Once we understand what the tool is for, we may find that we can do it better, or that the way it works in Photoshop isn't suitable for GIMP's interface, or that GIMP already supports the feature, but in a different way. Once the feature has been discussed on the mailing list, a bug report should be opened so that record can be kept on its progress. Sven Neumann has this to say on the matter of a "polygon select" feature requests: * No tool should be written without doing a full specification beforehand and discussing this spec on the mailing-list(s). Bugzilla is the wrong place for such a discussion. If you want to do something to help, please make a list of usage scenarios that involve creating polygonal selections. Then analyze how these scenarios can be performed using the existing tools and identify problems. With the list of scenarios and problems, you are then able to analyze and to compare different possible solutions. These solutions might involve changing existing tools or adding new one(s). As soon as we have identified the best solution, it can be fully specified. Only then can someone can start to implement it. Plug-Ins What are plug-ins? Plug-ins are external modules that actually do the nifty graphics transformations. There is a plug-in registry at [url]http://registry.gimp.org/[/url] with the latest plug-ins, maintained by Ingo Lütkebohle. [Special thanks to Adam Moss for the original registry!] How do I add new plug-ins? First, copy the plug-in[s] to your plug-in directory (typically /usr/local/lib/gimp/$VERSION/plug-ins/). After copying the plug-in to its proper directory, just run GIMP. It should automatically find new plug-ins. How do I build new plug-ins? You'll need a copy of the source directories. Build GIMP. Place the new plug-in in the plug-ins directory. The docs with the new plug-in hopefully identify any special libraries it needs. Look for a plug-in with similar libraries (if all else fails, look at xpm and whirlpinch). With newer versions, if the plug-in is contained in a single source file, you should just have to run gimptool in the plug-in's directory : * gimptool --build plugin.c For older versions, there are several methods. The first two walk you through a number of steps manually; these are the most thorough, but also require more work on your part. The last ones are scripts of one sort or another, and are easier on your part -- if they work with your system. Go ahead and try - you can always fall back on the first methods. * The best way to procede is to edit the Makefile. Pick a similar plug-in (such as whirlpinch). For the SRC and OBJ lines, just add entries similar to the others, but with the new plug-in's name. Now, find all the groups of lines with the other plug-in's name in them, duplicate them, and change the old name to the new name. The one exception is the huge set of lines that have a lot of paths that end in .h - do not bother with these. Now, just type o make + and it should build. Install it wherever your other plug-ins are installed. * A second choice for those who don't want to mess with the main Makefile is to build a file to create just the new plug-in. Start the same way - pick a similar plug-in. Now remove the binary and object files for the one you just picked. For instance, if you selected the whirlpinch plug-in, you will see the following files: o whirlpinch whirlpinch.c whirlpinch.o + In this case, you would remove the first and last files, leaving the whirlpinch.c file. Now type make + to rebuild the old plug-in. Copy the output (cut and paste it!) into a file. Edit the file and change all occurances of "whirlpinch" (or whatever) to the name of the new plug-in. Execute the file you just edited. For instance, if the file is make_plug-in, just type make_plugin + and it should work. The copy the plug-in to wherever the others are installed on your system. * A Makefile o First, load Makefile-pi provided by Ciccio C. Simon . Change all occurances of the word sharpen in Makefile-pi to the name of the new plug-in. Then type o make -f Makefile-pi + and watch it (hopefully) work. If it doesn't work, try the next method. * A compile script o First, load the compile-pi script provided by Jeremy Dinsel . Change the permissions on compile-pi as follows: o chmod ugo+rx compile-pi + and type compile-pi help + for instructions. Follow those instructionms. If this one also fails, go back to the earlier, manual methods; you have too picky a configuration for the simple methods to work. If you need more help, ask your system administrator or a handy programmer, or get a good book on make (such as O'Reilly's). You may want to join the GIMP developer's list as well (see the Developer FAQ). Is there a plug-in for ... ? The plug-in registry referenced above is the place to check. Why did some plug-ins disappear for 0.99.19? Some of the plug-ins have proven unstable. These have been moved into a separate download, which should be available wherever you got the GIMP, in the file gimp-plugins-unstable-VERSION.tar.gz or gimp-plugins-unstable-VERSION.tar.bz2 . Since this list may change frequently, the unstable plug-ins are no longer listed here. Script-Fu What is Script-Fu? In the words of S&P: * Script-Fu is the first GIMP scripting extension. Extensions are separate processes that communicate with the GIMP in the same way that plug-ins do. The distinction is that extensions don't require an active image to operate on, instead extending GIMP's functionality. GIMP internals for version 1.0 have been completely overhauled from version 0.54. In particular, the plug-in API has been made far more general with the advent of the procedural database (PDB). The PDB allows GIMP and its plug-ins to register procedures which can then be called from anywhere: internally, from extensions, and from plug-ins. There are already over 200 internal GIMP procedures, and more being created all the time. Because all of these procedures can be easily invoked from extensions, the logical next step was to create a scripting facility; thus, Script-Fu was born. Where can I learn about Script-Fu? As with plug-ins, web pages, COBOL, or anything else, one of the best things you can do is look at other peoples' code, and play with it. But it helps a lot if you know Scheme. * = S&P's Script-Fu pages at [url]http://www.xcf.berkeley.edu/~gimp/script-fu/script-fu.html[/url] = Mike Terry's Black Belt School of Script-Fu at [url]http://manual.gimp.org/manual/GUM/write_scriptfu3.html[/url] How do I call one script-fu script from another? The trick to calling script-fu-scripts from another script is to just reference the main define for the script and not to try to use the pdb call. All the scripts in script-fu share a common name space; you call other scripts just like a regular function / define / whatever you call those those things in_scheme. Ie, to call script-fu-predator in a script, just use * (script-fu-predator img drawable 2 TRUE 3 TRUE TRUE) For examples, see * [url]http://adrian.gimp.org/scripts/test.scm[/url] . How do I call a plug-in from script-fu? The following examples assume the plug-in name is "plug_in_randomize_hurl", and the plug-in has four parameters specific to it, the first two of which are floats, and the next two ints. From the script-fu console, call a plug-in like this: (plug-in-name 1 0 0 100.0 1.0 10 0) The first parameter should always be a "1". The next two are the image number and drawable. Anything following these numbers will be plug-in parameters, which depend on the plug-in. Inside an actual script, call a plug-in like this: (define (script-fu-fred img drawable) (plug-in-randomize-hurl 1 img drawable 100.0 1.0 10 0) (gimp-displays-flush) ) (script-fu-register "script-fu-fred" "<Image>/Script-Fu/fred" "Randomize test" "Miles O'Neal <meo@rru.com>" "Miles O'Neal" "1998/May/1" "RGB*, GRAY*, INDEXED*" SF-IMAGE "Image" 0 SF-DRAWABLE "Drawable" 0) How do I execute script-fu from batch mode? Invoke the script as non-interactive and add a pair of escaped quotes around each string just like you do in (script-fu-register). You DO NOT need to replace '-' with '_' in any names or registrations. Example script: (define (script-fu-famhist-link text filename) ;; code ommitted for brevity (file-gif-save 1 img 0 filename "" FALSE FALSE 0 0)) (script-fu-register "script-fu-famhist-link" "<Toolbox>/Xtns/Script-Fu/Family Historian/Link" "Family Historian Link" "John Johnson" "John Johnson" "1998" "" SF-VALUE "Text String" "\"Family Historian\"" SF-VALUE "Base filename" "\"foo\"") Example Invocation: ;; note the '1' as the first argument tell it to run non-interactivly ;; note the \" \" pairs around the strings gimp -n -b '(script-fu-famhist-link 1 "\"Introduction\"" \ "\"intro.gif\"")' '(gimp-quit 0)' For a detailed, step by step explanation, check out Adrian's GIMP Batch Mode how-to at [url]http://adrian.gimp.org/batch/[/url] . What does ``procedural-database-error'' in script-fu mean? Normally it means that the script is trying to use a particular font that isn't available on your system - it's either not installed or not in your X server's FONTPATH. The base script-fu package makes extensive use of the freefont package, and at least one font (AlfredDrake) from the sharefont package. What is Net-Fu? Where is it? Net-fu is a web-based interface to a script-fu server. The work is done at a remote site. To see Net-fu, point your web browser at [url]ftp://ftp.gimp.org/[/url] or one of the miiror sites, and then go to "gimp/net-fu/". Any web browser can read net-fu pages; the browser must be Java-enabled to actually run Script-fu. Fonts Where can I get the fonts I'm missing? The freefonts and sharefonts packages are both available from [url]ftp://ftp.funet.fi/pub/Linux/mirrors/metalab/X11/fonts/[/url] or other metalab mirrors. If you get the sharefonts package, be sure and read the various licensing agreements, and abide by them. How can I change the GIMP font? You need to copy the gtkrc file that comes with the GIMP source (in the top level directory) into $HOME/.gimp/gtkrc . As of 0.99.10, this should be recognized. You then go in and edit the default font style, the one that looks like this: style "default" { font = "-adobe-helvetica-medium-r-normal--*-100-*-*-*-*-*-*" } I'm sure ther's a lot of clever stuff that can be done here, and I'll try to track it down soon, but in the meantime, just change that "100" to something larger, like "120" or "140". (The number is points= 10, so 100 is a 10 point font). Obviously, you could stick in any font you have available. Why don't the Far Eastern fonts work? These are 16 bit fonts, with thouousands and thouousands of characters. And the characters are more complex, which means (usually) more bits per character, which means more memory and more processing time. This includes fonts such as kana, kanji, song ti, mincho and gothic. (If you look carefully at the fully qualified font name for gothic via xfontsel, you'll see clues. It's a daewoo font. The gothic name is misleading to western minds, but no doubt means something to its author[s].) Check one of these out in a program that shows a font as pages (such as xfd).. You can keep hitting next page to see a new page of characters, almost forever. What about TrueType fonts? If neither your X server nor your X font server supports you can try one of the TruType font servers: xfstt ([url]http://sunsite.unc.edu/pub/Linux/X11/fonts/[/url]) or xfsft ([url]http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/[/url] . xfstt supposedly has limitations on the font size. File Formats What is GIMP's native graphics file format? XCF is GIMP's "native" format. This will preserve all information about an image, including the layers. What other graphics file types are supported? All the common formats, and many more as well, including GIF, TIFF, JPEG, XBM, XPM, PostScript, and BMP. Plug-ins are used to load and save files so adding new file types is very simple, compared to other graphics programs. As of July 1, 1998, the list of supported types included BMP, CEL, FITS, FLI, GBR, Gicon, GIF, GIcon, HRZ, JPEG, PAT, PCX, PIX, PNG, PNM, PostScript, SGI, Sun Raster, TGA, TIFF, XPM, XWD and XCF. Bzipped, Gzipped and Xdelta'd files are understood, and URL support is provided. Of course, plug-ins for other types may be available at the plug-in registry . * *[/s][/s][/QUOTE]
Your name or email address:
Do you already have an account?
No, create an account now.
Yes, my password is:
Forgot your password?
Stay logged in
Coin Talk
Home
Forums
>
Coin Forums
>
Coin Chat
>
New camera shots.
>
Home
Home
Quick Links
Search Forums
Recent Activity
Recent Posts
Forums
Forums
Quick Links
Search Forums
Recent Posts
Competitions
Competitions
Quick Links
Competition Index
Rules, Terms & Conditions
Gallery
Gallery
Quick Links
Search Media
New Media
Showcase
Showcase
Quick Links
Search Items
Most Active Members
New Items
Directory
Directory
Quick Links
Directory Home
New Listings
Members
Members
Quick Links
Notable Members
Current Visitors
Recent Activity
New Profile Posts
Sponsors
Menu
Search
Search titles only
Posted by Member:
Separate names with a comma.
Newer Than:
Search this thread only
Search this forum only
Display results as threads
Useful Searches
Recent Posts
More...
