My latest Restoration
https://www.flickr.com/photos/115367823@N05/31009882065/sizes/c/

Original size
https://www.flickr.com/photos/115367823@...5/sizes/o/

Every time i need to make a layer greyscaled, i need to load the layer as a whole new project, Image -> Mode -> greyscale, then convert back to RBG. Export it. Then load that image as a new layer to my project.

Can i simplify this more to just convert a layer to greyscale?

I guess its something like wingdings, but im unsure if wingdings 3 is a commercial font or not.

Want to make something like this with text along path.

   

This is a thread for GIMP 2.8 themes. They are NOT suitable for use on GIMP 2.10


The 32x32 Symbolic theme is here:
https://bitbucket.org/paynekj/paynekj-gi...-Big-32.7z

The 32x32 Colour Theme is here:
https://bitbucket.org/paynekj/paynekj-gi...olor-32.7z

The 48x48 Symbolic theme is here:
https://bitbucket.org/paynekj/paynekj-gi...-Big-48.7z

The 48x48 Colour Theme is here:
https://bitbucket.org/paynekj/paynekj-gi...olor-48.7z

The 32x32 Dark Symbolic theme is here:
https://bitbucket.org/paynekj/paynekj-gi...32-Dark.7z

The 48x48 Dark Symbolic Theme is here:
https://bitbucket.org/paynekj/paynekj-gi...48-Dark.7z


These are all archived in .7z format and will need to be extracted into your personal profile Themes folder.

Please use this thread to report any issues (missing icons etc)

Note that at present I cannot find any way to change the Document History icon.

There is also an issue with the default colours and swap colour icons: https://bugzilla.gnome.org/show_bug.cgi?id=739469 which limits how big they can be.

For comparison, the Default, Color-32 and Color-48 themes:
   

The symbolic themes:
   

The dark symbolic themes:
   

https://github.com/alexjc/neural-enhance

Bumpmapping is probably the classic way of bevelling text (the "modern way" is using layereffects).

One thing that always seemed a bit unrefined is that the blurred bumpmap spreads the bevel outside the text boundaries.

But there are ways to take bumpmapping to the next level, and reading the WOW Book just made me remember a few tricks.

1.) For the first example we bumpmap text into a grey (#8080808) layer.
The values im using are 120 for the Azimuth and 30 for the Elevation.

The bumpmap has a  Blur of 1px and im using a Depth of 3. We are getting an emboss effect.

   

2.) Here im using a Depth of 8 and an Ambient of 100. The bumpmap has been blurred 8px.
This is your basic bumpmapping technique.

   

3.) Now we are getting a bit clever and trim our edge. We are still using the 8px blurred bumpmap, but now we are calling up a selection of the original text, invert it and fill with black, so that we get a hard edge. On top of that we apply another Blur of 1px to smooth things out.
Heres what it looks like:

   

4.) For a chisel effect, we use our trimmed bumpmap, call up the original text selection and shrink it (i used 3px), then fill with white. This gives the blur an edge.

   

5.) For our final trick we apply a curve to the bumpmap, blur it by 4px to smooth everything out, and get this contoured edge:

   

Not really a new baby, since it is an improvement on my previous path-ladder script, but it comes with some interesting new options. Basically, it draws lines (in orange, below) between two paths.

   

Available at the usual place.

Enjoy.

It never ceases to amaze me that my most downloaded (and by a huge margin) script (outside the path ones) is ofn-file-next. 20-30 downloads a week and counting. And the only use of the script is processing manually long sequences of images. WTF are so many people doing with it?

So i was thinking about selling stuff for Gimp and Inkscape in the future.

Do you think it is against the spirit of open source programs and the Gimp community ?

I was thinking about special tutorials, including gradients, brushes, vector elements, etc.
Of course all stuff i made myself.

Chris Hildenbrand from 2dgameartguru.com seems to have some success with it considerig the feedback he gets.
I have donated a few bucks here and there for people like him and i think its fair to give something back for all the free stuff he is sharing.

I'm considering repackaging together a bunch of small scripts that perform rather simple operations on paths: delete strokes, decompose the path, splice strokes, etc... to make a simple path edition toolbox.

The goal is to include simple editing steps

• that don't require dialog input
  
• that perform tasks that are either impossible to do by hand and that can do them significantly faster (cut-off point would be 3-4 clicks without a script)
  

• delete strokes: delete strokes with an end in the selection.
  
• extract strokes: keep strokes with an end in the selection.
  
• reverse strokes: swap stroke end to end (no visible result but often useful).
  
• splice strokes: connect together strokes with end points sufficiently close.
  
• cut strokes: cut strokes on the anchor point in selection (this is the opposite of the "splice" above, a stroke with thee anchors will produce two strokes of two anchors, where two anchors will coincide)
  
• intersect strokes: cut and splice two strokes where they intersect. The $64K question is to have a good criterion to determine which of the 4 angles to keep.
  
• decompose strokes: decomposes a path into its individual strokes. Unlike the rest this one would create additional paths.
  
• summary: show a summary of the path information (to check that what you got is actually what you see).